Over a million developers have joined DZone.

Why I Use Node.js

Node.js is great for: applications with heavy I/O, bootstrapping, its easy set-up, its growing ecosystem and infrastructure.

Evolve your approach to Application Performance Monitoring by adopting five best practices that are outlined and explored in this e-book, brought to you in partnership with BMC.

It has been a while since I took up Node.js development.

My early impressions were pretty positive and after some months of Node.js development I have to say that I am amazed.

There are many reasons to continue using Node.js for my projects.

Great for Applications with Heavy I/O

The asynchronous nature of Node.js enables you to stay focused on your implementation. You don’t need to proceed to any extra configurations as you do with multithreaded environments. Also, long I/O operations don’t have to be dispatched to any custom mechanisms, enabling you to avoid any extra costs on development.

Provided your application is mostly based on I/O and less on computation, chances are that Node.js will work for you.

Bootstrapping

Node.js is one of the best bootstrapping experiences that I have had with a programming environment. All you need is to have node and npm installed. There are libraries for almost everything you need and the configurations needed are minimal.

Also, getting started with the implementation of your Node.js extension takes you no time at all.

Set-Up Simplicity

All it takes to setup your project is your source code and a package.json file with your dependencies.

Make Use of Your JavaScript Skills

Though a backend developer, I had to write some JavaScript in the past. The same applies to other developers I know, even to the most backend-focused. Learning a language is an investment. You can make more out of your JavaScript knowledge by using Node.js on your projects provided it suits to their needs.

Not Another Web Framework

Node.js is not another web application framework. Due to its asynchronous nature and efficiency it can be applied to many problems. For example, it can be used as a glue among components of your infrastructure. Also, due to heavy development you don’t just have a runtime environment, you have a whole ecosystem with tools that apply to a wide variety of problems.

Conclusion

Node.js is already a part of the tools that I use on a daily basis. However, it should be used wisely and make sure that it fits your project’s nature.

It is really challenging to deal with the callback hell, but in exchange you get a pretty promising and fast-growing ecosystem.

Learn tips and best practices for optimizing your capacity management strategy with the Market Guide for Capacity Management, brought to you in partnership with BMC.

Topics:
node.js ,i/o ,input-output ,javascript ,bootstrapping ,performance ,web frameworks

Published at DZone with permission of Emmanouil Gkatziouras, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}