Why and when to use Node.js? [duplicate]

by

It’s evented asynchronous non-blocking I/O build ontop of V8.

So we have all the performance gain of V8 which is the Google JavaScript interpreter. Since the JavaScript performance race hasn’t ended yet, you can expect Google to constantly update performance on V8 (for free).

We have non-blocking I/O which is simply the correct way to do I/O. This is based on an event loop and using asynchronous callbacks for your I/O.

It gives you useful tools like creating a HTTP server, creating a TCP server, handling file I/O.

It’s a low level highly performant platform for doing any kind of I/O without having to write the entire thing in C from scratch. And it scales very well due to the non-blocking I/O.

So you want to use Node.js if you want to write highly scaling and efficient applications using non-blocking I/O whilst still having a high level scripting language available. If needed, you can hand optimise parts of your code by writing extensions in C.

There are plenty of OS libraries for Node.js that will give you abstractions, like Express.js and now.

You don’t want to use Node.js if you want (slow) high level abstractions to do everything for you. You don’t want to use Node.js if you want RAD. You don’t want to use Node.js if you can’t afford to trust a young platform, either due to having to write large pieces of code yourself to do things that are build into other frameworks or because you can’t use Node.js, because the API isn’t stable yet or it’s a sub 1.0 release.

More Related Contents:

  1. nodejs vs node on ubuntu 12.04
  2. Send message to specific client with socket.io and node.js
  3. How does setTimeout work in Node.JS?
  4. Node.js and CPU intensive requests
  5. How to decide when to use Node.js?
  6. Execute a command line binary with Node.js
  7. return value after a promise [duplicate]
  8. garbage collection with node.js
  9. Javascript ES6 TypeError: Class constructor Client cannot be invoked without ‘new’
  10. async for loop in node.js
  11. Why do I need to await an async function when it is not supposedly returning a Promise?
  12. How to use optional chaining in Node.js 12
  13. Discord bot on Heroku throws an error: agent ??= new https.Agent
  14. Are there still reasons to use promise libraries like Q or BlueBird now that we have ES6 promises? [closed]
  15. How to run Puppeteer code in any web browser?
  16. Proper way to skip a then function in Q Promises
  17. Uncaught TypeError: Object.values is not a function JavaScript
  18. How is Node.js inherently faster when it still relies on Threads internally?
  19. browserify error /usr/bin/env: node: No such file or directory
  20. Sharing websocket across browser tabs?
  21. Failed to load resource from same directory when redirecting Javascript
  22. What does “this” mean in a nodejs module?
  23. multer – req.file always undefined
  24. Javascript’s .includes function not working correctly with array of objects [duplicate]
  25. Node.JS How to set a variable outside the current scope
  26. Properly batch nested promises in Node
  27. How can I use webpack with express?
  28. ASYNC / AWAIT SyntaxError: await is only valid in async functions and the top level bodies of modules
  29. How to apply both ValidationPipe() and ParseIntPipe() to params?
  30. Approach to multiple MySQL queries with Node.js

Leave a Comment