News for hackers. Stuff that matters.
Re:600k concurrent websocket connections on AWS using Node.j... by monus21 on Friday October 11, 2019 @09:40AM (#21224220)
It's not about which is the best technology. The barrier to entry for Node.js is next to nothing and the size of the ecosystem is incomparable to Elixir. Which means tons of companies will go with Node and feed back to the ecosystem and so on...
Re:600k concurrent websocket connections on AWS using Node.j... by mtberatwork on Friday October 11, 2019 @12:59PM (#21226199)
If we are going on size of ecosystem/what companies are invested in/etc, then you may as well stick with Java and the JVM with something like Vert.x. No need for Node.
Re:600k concurrent websocket connections on AWS using Node.j... by PunchTornado on Friday October 11, 2019 @05:24PM (#21228612)
nodejs ecosystem is much larger than the java one. also the amount of money companies invested in node is at least on par with java. think only about google chrome.
Re:600k concurrent websocket connections on AWS using Node.j... by winrid on Saturday October 12, 2019 @11:12PM (#21238099)
There's no advantage to using Node in a lot of cases though. Maybe if you're creating a microservice to generate email html or something. Data/state management, stream/job processing? Java or Kotlin all the way.

I have written a lot of Node services. Spent six years doing it. Gimme Java plz.

Re:600k concurrent websocket connections on AWS using Node.j... by viraptor on Friday October 11, 2019 @05:33PM (#21228694)
> The barrier to entry for Node.js is next to nothing

Assuming existing experience with JS / npm / async style. If you don't have that, I'm not sure which would be harder to start with. Given a little bit of experience with each, I'd actually lean towards elixir being a simple choice. Then again it depends on whether you're cool with training new devs in case of lack of elixir people.