What are some architectural reasons to use node.js aside from scalability?


The most common theme I read about why to use node.js is for high scalability due to it’s evented, non-blocking I/O model. I’m trying to understand other non-scalability uses cases (and aside from being used as a general server-side javascript engine).

  1. Does node.js have other use cases if scalability isn’t a concern of mine?
  2. If yes to #1, what are they?
  3. Is node.js usage appropriate for any particular type of application architectures? E.g. similar to how some key/value (nosql — ugh I hate that term) databases are useful other than for scalability reasons.

Problem courtesy of: Howiecamp


I think this blog posts sums it up quite well: http://debuggable.com/posts/understanding-node-js:4bd98440-45e4-4a9a-8ef7-0f7ecbdd56cb

In short (pro node.js):

  • Speed
  • Javascript (especially if you know it already)
  • Efficiency

node.js is really great. Give it a try! :)

Solution courtesy of: petermanser

View additional discussion.