Recently we were asked why we recommend the use of Node.js on our project. While Stuart and I are putting together a presentation and working on a blog post, it got me wondering what it is about Node.js that I like so much and why we should use it.
When looking for arguments into why we should use Node.js in the enterprise, the following benefits get attributed to using it, in brackets are the companies that have attested these benefits:
- Massive performance gains (LinkedIn, Groupon, PayPal, Walmart and Ebay)
- Great for Mobile development (Walmart and Yahoo)
- Vibrant community
- Built from day one around Async model and event driven
- Easier to find people that can work on Node than say Erlang
- Contributors are maturing
When it comes to the performance claims, we need to put together a pretty consistent story that backs a lot of these statements and disavows the others. When looking into this for our presentation, the information is spread across tweets and blog posts. TO convince Enterprise decision makers, I think we would need something more cohesive.
While this quote relates to Go it’s still relevant as it relates to async programming:
An asynchronous model had many other benefits. We were also able to instrument everything the API was doing with counters and metrics, because these were no longer blocking operations that interfered with communicating to other services. We could downsize our provisioned API server pool by about 90%. And we were also able to remove silos of isolated Rails API servers from our stack, drastically simplifying our architecture.
The vibrant community claim are both a benefit and a detriment. I find the rate of change and churn dizzying at times. I think Neal Ford put it well when discussing the ThoughtWorks’ Technology Radar:
It is proving difficult to ignore the new shiny and this is compounded by other people’s enthusiasm for experimenting with new tools and frameworks. This can have an impact on productivity as you can be forever adopting and re-writing things and it requires discipline to evaluate the tools and when to apply them to a project. On the plus side, it shows the community is driving change and improvements.
On the flip side there are however still a lot of common misconceptions:
- Just a JS Dev, which is clearly not true. JS Devs are just as Software Engineering focused as Java Developers. This is evident in the maturing of contributors to Open Source projects
- It’s a server. Again not true, it’s more akin to a JVM or runtime
- It is slow. I think those days are behind us – measure it – V8 is fast, as are many other engines (Shakra/Spidermonkey, etc…), Nashorn JVM based JS engine is also available
Let’s consider some other advantages:
- Cross skilling between front end and back end teams, between the whole team. We blur the boundaries between front and back end specialists, and this to me is a good thing. It also helps with pluging knowledge gaps and knowledge being concentrated with one team member or area of the team
- It has a pretty decent package management system with NPM
- It’s a foundation (backed by Joyent, IBM, PayPal, Microsoft, Fidelity and the Linux Foundation)
To expand a little on the NPM point. If you consider Modularisation and NPM, you find yourself in a win win situation.
Modularization via Node Modules was a big win as well, as we were able to share components across teams and easily manage them through a NPM
Smaller/modular code is easier to maintain and debug. More modular code, is more composable and indeed more re-usable.
There are many things that speak to Node.js being a great choice for developing and delivering applications across the spectrum of businesses. I hope I have also made a few points that back up why this is a great platform to work and have fun delivering solutions with.