Can Node.js be used in banking and financial apps which involve lots of transactions?
So far it seems Java is perfectly suited for these apps. I was wondering, if there is any real limitations in Node.js when it comes to these kinds of apps.
well I guess you can use a lot of things :) ... and if you use it just as the app delivery system and the transactions are handled in a typesafe language I would not be against it ....
nodejs has some cool advantages but I personally would not relay my financial calculations to a language does not implement decimals but floats. which leads to stackoverflow.com/questions/588004/is-floating-po…
but for a client which does not do any calculations I would use. the transaction bottleneck usually is the database because it's the ultimate point of truth.
oh and one more remark ofc you can handle it .... but if you grow, likely the amount of developers grow and this is about money .... so not many people are willing to put the risk of not type safe languages on money applications, that's because at some point not all developers have the overview.
A rounding issue can cost you millions in no time. in one company we had a rounding issue which was minimal but did cost the company 45k € over 8 years ....
j
stuff ;)
well I guess you can use a lot of things :) ... and if you use it just as the app delivery system and the transactions are handled in a typesafe language I would not be against it ....
nodejs has some cool advantages but I personally would not relay my financial calculations to a language does not implement decimals but floats. which leads to stackoverflow.com/questions/588004/is-floating-po…
but for a client which does not do any calculations I would use. the transaction bottleneck usually is the database because it's the ultimate point of truth.
oh and one more remark ofc you can handle it .... but if you grow, likely the amount of developers grow and this is about money .... so not many people are willing to put the risk of not type safe languages on money applications, that's because at some point not all developers have the overview.
A rounding issue can cost you millions in no time. in one company we had a rounding issue which was minimal but did cost the company 45k € over 8 years ....