600k concurrent websocket connections on AWS using Node.js (2015) • Hacker News Board

Re: 600k concurrent websocket connections on AWS using Node.js (2015)

#21

Post by runj__ » Fri, Oct 11, 2019, 1:29 PM UTC

anildigital wrote: post #19

I don't get point of using Node.js when compared to something like Elixir. Elixir's Phoenix can handle more numbers of concurrent connections as well as provide reliability with better programming abstractions, distribution, pretty good language.

Because javascript is one of the most popular programming languages in the world and the pool of Elixir programmers is almost non-existent?

Re: 600k concurrent websocket connections on AWS using Node.js (2015)

#22

Post by anildigital » Fri, Oct 11, 2019, 1:31 PM UTC

runj__ wrote: post #21

anildigital wrote: post #19

I don't get point of using Node.js when compared to something like Elixir. Elixir's Phoenix can handle more numbers of concurrent connections as well as provide reliability with better programming abstractions, distribution, pretty good language.

Because javascript is one of the most popular programming languages in the world and the pool of Elixir programmers is almost non-existent?

From this https://www.ycombinator.com/topcompanies/ Brex, Podium, PagerDuty use Elixir. They are in top YC companies, not a surprise.

Re: 600k concurrent websocket connections on AWS using Node.js (2015)

#23

Post by truth_seeker » Fri, Oct 11, 2019, 1:31 PM UTC

There is more performant web-socket implementation than the one mentioned in the blog. It can handle 6X more connections and much less memory

https://github.com/uNetworking/uWebSockets.js

EDIT:

Note that the blog post is from 2015. There are many optimization (Ignition and TurboFan pipeline) has been done in V8 since then, especially offloading GC activity to separate thread than NodeJS Main thread.

Re: 600k concurrent websocket connections on AWS using Node.js (2015)

#24

Post by IggleSniggle » Fri, Oct 11, 2019, 1:32 PM UTC

anildigital wrote: post #19

I don't get point of using Node.js when compared to something like Elixir. Elixir's Phoenix can handle more numbers of concurrent connections as well as provide reliability with better programming abstractions, distribution, pretty good language.

I am totally with you on Elixir/ Phoenix. But using Node.js is about leveraging frontend devs to get productive on the backend fast. At least, I think that’s the idea. Maybe also leveraging Google’s dependence on V8 (and thus all the engineering love it gets), although I don’t think that’s really a great argument compared to the EVM.

Re: 600k concurrent websocket connections on AWS using Node.js (2015)

#25

Post by IggleSniggle » Fri, Oct 11, 2019, 1:33 PM UTC

anildigital wrote: post #22

runj__ wrote: post #21

Earlier quoted context omitted.

Because javascript is one of the most popular programming languages in the world and the pool of Elixir programmers is almost non-existent?

From this https://www.ycombinator.com/topcompanies/ Brex, Podium, PagerDuty use Elixir. They are in top YC companies, not a surprise.

Thanks for pointing those out. I would really like to switch to Elixir in my day job.

Re: 600k concurrent websocket connections on AWS using Node.js (2015)

#26

Post by [deleted] » Fri, Oct 11, 2019, 1:33 PM UTC

np_tedious wrote: post #20

anildigital wrote: post #19

I don't get point of using Node.js when compared to something like Elixir. Elixir's Phoenix can handle more numbers of concurrent connections as well as provide reliability with better programming abstractions, distribution, pretty good language.

I don't understand people eating hot dogs. Hamburgers have...

[deleted]

Re: 600k concurrent websocket connections on AWS using Node.js (2015)

#27

Post by runj__ » Fri, Oct 11, 2019, 1:34 PM UTC

anildigital wrote: post #22

runj__ wrote: post #21

Earlier quoted context omitted.

Because javascript is one of the most popular programming languages in the world and the pool of Elixir programmers is almost non-existent?

From this https://www.ycombinator.com/topcompanies/ Brex, Podium, PagerDuty use Elixir. They are in top YC companies, not a surprise.

Do you think they got big because they use it or do they use it because they're big?

Pre-optimization is the root of all evil, my dude.

Re: 600k concurrent websocket connections on AWS using Node.js (2015)

#28

Post by anildigital » Fri, Oct 11, 2019, 1:37 PM UTC

runj__ wrote: post #27

anildigital wrote: post #22

Earlier quoted context omitted.

From this https://www.ycombinator.com/topcompanies/ Brex, Podium, PagerDuty use Elixir. They are in top YC companies, not a surprise.

Do you think they got big because they use it or do they use it because they're big? Pre-optimization is the root of all evil, my dude.

@runj__ You should read this blog post by Brex founder. He really says how Elixir suited well to the problem they were trying to solve https://medium.com/brexeng/why-brex-chose-elixir-fe1a4f31319...

Re: 600k concurrent websocket connections on AWS using Node.js (2015)

#29

Post by dgelks » Fri, Oct 11, 2019, 1:38 PM UTC

RossM wrote: post #2

Interesting details; it would be nice to see how those ulimit/networking numbers were arrived at. The title should have [2015].

Yep - title should've had [2015], my bad!

Re: 600k concurrent websocket connections on AWS using Node.js (2015)

#30

Post by monus21 » Fri, Oct 11, 2019, 1:40 PM UTC

anildigital wrote: post #19

I don't get point of using Node.js when compared to something like Elixir. Elixir's Phoenix can handle more numbers of concurrent connections as well as provide reliability with better programming abstractions, distribution, pretty good language.

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...