4 ms·
Could someone unpack and explain this answer snippet a bit? I personally do not believe that Node is a viable platform for building multi-user server l
by mixmastamyk 11y ago
Could someone unpack and explain this answer snippet a bit?
I personally do not believe that Node is a viable platform for building
multi-user server logic. Node is great for asynchronicity, but that
shouldn't be confused with concurrency* which is really what you want in
those scenarios (I can write a list of things Node doesn't do well for
building safe backend systems, but that's one example).
The Node platform is very good for single-user applications (games, web
apps, command line tools, "browserified" apps, Node+browser containers),
but I think a lot of people will come to regret using it for bigger
back-ends.
A company I work with occasionally is building a backend and client system in node+mongo, and I wonder if it is a good idea. The backend will be an app catalog of sorts, while the client will run these apps, which will animate stuff in a browser.
I've read lots of warnings about mongo, and now this. I'm torn about these choices, I've tried and liked them, but am a bit out of my element as primarily a python/c developer.
- ddebernardy 11y agoThese articles on Node unpack the point to some extent: - http://stackoverflow.com/q/22644328/417194 http://stackoverflow.com/q/22644328/417194 - http://www.future-processing.pl/blog/on-problems-with-threads-in-node-js/ http://www.future-processing.pl/blog/on-problems-with-thread... - http://web.archive.org/web/20120911094357/http://dev.hasenj.org/post/31042963934/nodejs-hate http://web.archive.org/web/20120911094357/http://dev.hasenj.... - https://news.ycombinator.com/item?id=4495101 https://news.ycombinator.com/item?id=4495101