There's no good reason to use Nodejs(bysin.net) |
There's no good reason to use Nodejs(bysin.net) |
Video: https://vimeo.com/44312354
Slides (PDF): http://www.erlang-factory.com/upload/presentations/558/efsf2...
That's just to warm up. How about 10+ million connections per box (Java + CentOS + enterprise box)? https://mrotaru.wordpress.com/2015/05/20/how-migratorydata-s...
For a given real use-case communication pattern, there will be different optimizations and approaches to squeeze peformance out of client and server hardware. (No 1SFA, YMMV.)
App boxes are usually pretty easy to scale up (and cheap). The efficiency of your app layer in terms of I/O is very rare the bottleneck for a scaled application.
The best reasons to use Node.js: - Single language for FE and Backend. Easier to recruit and build things. - Much faster to build things, on average, than in Go (or especially C++)
I'm not saying it's great, or better than Go/Rust/etc. It has obvious weaknesses, but to say "There's no good reason" is to only view development from one perspective.
Sound like the 2017 version of "Rails doesn't scale" - obviously you can make EVERYTHING scale.
Plus, saying 'never' in a programming context is never a good idea...
I think we can safely ignore hiSegmentation fault (core dumped).