Usually the more complex systems that use Java are going to hire more experienced/better devs. So higher pay.
Usually the more complex systems that use Java are going to hire more experienced/better devs. So higher pay.
Node excels at getting to market quickly with reasonable performance. I'm not really sure how to answer the performance question, because other than LuaJIT it's one of the fastest scripting languages.
> like a proxy or something?
For me, a proxy is better suited to Go. I've been building REST servers and websocket servers in Node.js though.
Not only did the "real" team try and gaslight me into thinking my implementation didn't work (It did, they copied it wrong), but it took 3 engineers twice the time it took to copy my work into Java as it did for me to do the original development. The kicker: The Java process was so bloated it took nearly 2x the compute resources to get the same throughput.
TL;DR I challenge every time someone says "This is complex/high throughput, so let's use Java instead of Node"
Also, just curious, what things from a data processing pipeline standpoint does Node do well in? What does it not do well in?
Would Java ultimately be the most scalable?
Could Node be as scalable in this regard?