Why Node.js is becoming the go-to technology in the Enterprise

By: Cian Ó Maidín

Over the last 18 months the use of Node.js has grown at an exponential rate.

It has moved from innovators such as Voxer  and Yammer  to a group of early adopters that are giving Node.js the credibility required to take it into the mainstream. E-Commerce giants WalMart and PayPal  have made big bets on Node while the likes of the world’s most read news publication: – The Mail Online  have implemented Node.js and Netflix are now in the process of implementing Node.js  too.



Rapid-Innovation and Delivery

Increasing competition between rival internet companies, the speed of delivery and the ability to iterate are the key traits of market leaders. In a competitive scenario, reacting to end user needs, incorporating their feedback into the offering and delivering updates and changes regularly is essential.


Developer Happiness

It’s extremely difficult to hire top talent these days; good developers like to learn new things and to use new technologies. The ability to make developers happy in your organisation cannot be underestimated, happy enthusiastic developers means better software, delivered with more passion by people that are having fun.

Bill Scott once told the story of a new hire that had the choice of going to work for Facebook or PayPal. Faced with similar offers and benefits the developer made his choice, and was quoted as saying.

“Why go to Facebook and do PHP when you can go to PayPal and do Node.js”

  • Bill Scott – Dir UX PayPal


Easy to attract and retain talent.

It’s true, you can do anything in Java! But what’s also true is that the best developers like to work using new and interesting technologies, developers want to work new technologies which enable more and allows ideas to be expressed quickly and easily.



PayPal reported: double the number of requests per-second and reduced response time by 35% or 200 milliseconds.

WalMart Labs had a bumper launch with Node.js in 2013, where they put all of their Mobile traffic through Node.js on black-friday, the busiest shopping period of the year.
The team at WalMart Labs live tweeted against #nodebf tag showing the performance of the Node.js application.

On Black Friday the WalMart servers didn’t go over 1% CPU utilisation and the team did a deploy with 200,000,000 users online.



Similarly Groupon re-implemented their system in Node.js which resulted in page load times dropping by a whopping 50%.

The old story of linkedin where moving to Node.js from Rails for their mobile traffic, reducing the number of servers from 30 to 3 (90% reduction) and the new system was up to 20x faster.

Easy to modify and maintain

New services development using Node.js is easy because of conventions that have grown with Node. Writing applications the Node-way means that applications are composed from small modules, which are piped together. Over-time traditional monolithic applications become rigid and difficult to adapt and as new requirements are added. Eventually traditional applications begin to creak under the weight and the stress put on them by the requirements they were not designed for.

With Node.js a group of small applications is developed instead of one large application, this enables a change to be made or new functionality to be added without requiring changes to be made deep inside the entire code-base.


Node.js programs are developed using JavaScript, this means that the silos that existed between frontend developers and backend developers are now broken down, and this results in significant efficiencies in the development process. With Node.js it’s possible to merge web and backend teams into one unit which makes things much more efficient. Node.js opens the door to a world where full stack developers make life much better by reducing inter-silo dependencies. Node.js also has a great package management system called NPM, it’s the first package systems for JavaScript to get dependency management right. NPM effectively kills the possibility of experiencing dependency hell. Node also has a vibrant user-land and a very large number of modules are available via Node.js’s package manager (over 60,000 and growing fast)

PayPal measured a 2x increase in developer productivity, where it took half the number of developers to deliver an application when compared to Java, and it was delivered in less time.


The Future of Node.js is bright

Eran Hammer announced at NodeDay that WalMart are planning to use Node.js across all eCommerce by the end of 2014.

PayPal are rolling out Node.js across their entire web application and Node.js will be used almost everywhere within 2 years.

Although Google have not publicly come out talking about their use of Node.js, there is evidence that they are using it, a simple search on linkedin shows almost 200 people in google with Node.js on their profile. According to an article on VentureBeat: “Googlers are definitely working on Node.js projects – perhaps even something big that will be released to the public in the near future. They’re just not ready to talk publicly about what that might be.”

Yahoo are a long way down the line with Node.js and have 200 developers doing Node.js full time with 800 public modules and 500 private ones.

New Entrants to Node.js such as Netflix and others show that there is big growth happening in this area at present.


Application Areas for Node.js

  • The Internet of Things
  • E-Commerce
  • Payment Processing
  • Social Media
  • Realtime Services
  • Media
  • Enterprise Web Service



 What if my business could:

  • Use ½ the number of developers to develop products
  • Reduce the number of servers needed to serve customers
  • Reduce Page Load Times by up to 50%
  • Hire top-level engineers ahead of big names like Facebook
  • Make customers happier
  • Make developers happier
  • Retain staff for longer

The answer is a no-brainer, the question is whether an enterprise would be crazy not to be considering Node.js in a very serious way.

For more information on using Node.js and it’s business benefits, talk to @nearForm

By: Cian Ó Maidín

Cian Ó Maidín is the co-founder and visionary CEO behind nearForm. Very early on, he saw how Node.js could help the world work in a better way. He is committed to making that happen through nearForm. He is an established entrepreneur, Node.js community leader, the creator of Node Dublin and the curator of NodeConf EU. In 2012, Cian was voted by the Sunday Business Post as one of the most influential leaders in Irish technology.
  • luglio7

    Impressive numbers.

    • Dimitri

      but look carefully at the numbers and the comparisons. Do a Google search on the web and yow will see that much of what is being said here is not down to Node.js at all.

  • http://andrearossi.eu/ Andrea Rossi


  • karatedog

    And if your project doesn’t use heavy database functions then you could choose MongoDB which also uses JS internally, and has a Javascript based shell.
    And the whole stack (frontend-backend-db) needs only one language skillset.

    • http://burstcreations.com Ilya Radchenko

      Or couchdb, which also is lighter and has a REST interface

      • http://seomadhat.blogspot.com/ Tecniche Avanzate SEO

        +1 per couchdb ^_^

      • pekhee

        I think CouchDB tries to abstract HTTP stuff, it’s hard to say that you can substitute it with DBs.

        It’s more like substituting NodeJS with CouchDB, however I believe these two together rock hard.

    • Mustafa Akın

      Or if you want to lose data, or switch back safe option on and have very low write performance across multiple servers

    • saad Mousliki

      WakandaDB could be also a good option ;)


    • nXqd

      I love the idea of using one language in whole stack. But it’s not true in real world application, at least for big ones.

      • Allan Ebdrup

        I ours it is. 10-14 devs working for 2 years, all JS (and 10 lines of make)

      • Colin Phillips

        Wallmart ,Linked In , Yahoo , PayPal not Big ?? , nodejs serves clients faster then any other server side language because of it’s architecture why would you not use it ?

    • Stefano Baghino

      I like both Node.js and MongoDB, but I’d be ware of any kind of monoculture. Not just because different programming languages, as different tools, give you a better option to tackle on certain kind of problems, but also because they tend to embrace different perspective and paradigms to different degrees. Being proficient in many, different programming languages enriches you and makes you a better developer.

  • http://eastasiastudent.net/ Hugh Grigg (葛修远)

    “With Node.js a group of small applications is developed instead of one large application, this enables a change to be made or new functionality to be added without requiring changes to be made deep inside the entire code-base.”

    This isn’t exactly new. OOP with good design principles is intended to achieve the same goal.

    • Allan Ebdrup

      but failed, that’s the difference

      • http://eastasiastudent.net/ Hugh Grigg (葛修远)

        You believe that OOP and Design Patterns are failures?

        • Stefano Baghino

          Their classical interpretation failed when a large and imposing culture formed on wrong premises and deviated from the initial goal of keeping it simple. Often, misusing object-orientation and design patterns lead to over-abstraction and complexity. Instead, the culture around Node has evolved in a way that smoothly transitioned good, theoretical, best practices of modularity and composability into actual enterprise development models.

        • Jason

          The same claim can be made about pretty much every new thing that appeared on the programming field in the last 50 years: procedural programming, mainframe virtualization, Unix, Erlang, OOP, Aspect Oriented Programming, SOA, and Node.JS itself.

          But those are just tools. As Stefano said, it all boils down to the culture and OOP became a playground for over-engineered code.

        • http://tracker1.info/ Tracker1

          Design patterns aren’t about applying a pattern every time it loosely fits though.. This tends to happen a lot in an “enterprise” development shop, often with .Net or Java. Not to mention that using Classes often leads to issues with tracking down the origin of a bug, or the nature of an issue. Testing becomes harder, which means adding layers of indirection and abstraction through interfaces, and even more indirection. I find that simple objects with functional utilities (which is how I write in js/node) tends to be cleaner and more easily tested.

          • M.

            I will give node.js at try, but frankly I doubt node.js will scale for complex (not large, but complex) projects without robust frameworks for dependency injection and testability. The strongly typed languages have two huge advantages in this regard: a compiler enforced type system that precludes large categories of common programming errors, and, I’m not joking here: a high barrier of entry that keeps cargo cult programmers from being too successful. Javascript is a good language, but it’s reputation has suffered from being a favorite of cut and paste script kiddies, much like the reputations of PHP and Visual Basic suffered.

            The fact that one of node.js’ main selling points is that it permits poor developers to write scalable code is a bad start: It is possible to write horrible crap in any language. You can brag about modular, single purpose design leading to good things, but it is also possible to crank out 10,000 components to implement a few hundred functional capabilities (sometimes several times over in slightly different ways) and end up with an un-maintainable, bug prone mess that is effectively “distributed spaghetti code” because there is no rhyme or reason to the architecture.

            I must also point out that many of these claimed “advantages” in node.js sound similar to basic principles that lie at the heart of modern OOP, best expressed in the SOLID principles (google it). Saying OOP has failed (because you apparently don’t understand the difference between modern, SOLID OOP and early conceptions of OOP (Animal -> Dog, Cat) that have been used for pedagogical purposes for the last 30 years simply proves you never groked OOP as it is currently practiced.

            As for being better for testability, that’s rich for a dynamic language like js: There is no better testing ecosystem than a strongly typed language, and C# is light years ahead of Java on that score because it has far stronger type system and Mocking frameworks. Strongly typed languages get test-ability by following patterns that have clear and unambiguous advantages: No non-injected external dependencies, a clear separation of concerns, depending upon abstractions instead of ‘concretions’, the single responsibility principle. Therefore good OOP programmers don’t “apply patterns every time it loosely fits” We start with patterns and compose larger structures that have particular characteristics, (e.g., extensibility & testability) much like a builder uses modular components to create a complex skyscraper that won’t fall down.

          • http://tracker1.info/ Tracker1

            I’ve worked on several very large projects in both C# and in node at this point… Even with good projects in C# I always found the programmatic abstraction of interfaces annoying… Mostly useful for testing… Will FP patterns with simple objects in JS, testing is easier and there’s no need for the abstractions…

            The worst I’ve seen in node, is when people try to bring in architectural concepts from Java or .Net designs into an environment where functional is a better fit.

            I’ve been building web applications since 1996. Recently a node/redis-cachr/cassandra system that handles over 300,000 requests per second with less than 100ms response time on 6 node/redis servers and 12 Cassandra.

  • Prasanth KP

    Javascript, Node.js, Mongo DB… Bright Future ahead for #JsDevelopers

    • Fail hard

      Mongo DB lol…

    • exfromtheleft

      the mean stack…

  • http://www.breek.fr/ Jérémy Chatard

    The numbers you give are impressive!

  • http://www.GreenIT.fr Green IT

    I’m very interested by that kind of figures from companies using node.js. Does anyone have some ?

  • drhowarddrfine

    “Writing applications the Node-way means that applications are composed from small modules, which are piped together. ”

    For 30 years I’ve been programming, we’ve always called that “the Unix way”.

    • Cian Ó Maidín

      10000% agree,

      Unix: build many small tools that work togther

      Emacs: build a tight core in C, build extensions in other languages

      Node.js is a combination of these.

      • Dimitri

        eh? This is not specific to Unix or Node.js. Small modules to work together LISP, Fortran, C. procedures, functions, objects are all written well in other languages too.

    • Naval Saini

      Cloud9′s open source code is a great example of the same. I love the way they have coded their software.

    • Jon Davis
  • Dimitri

    Someone should explain how reimplementing in node can result in “page load times” dropping by 50%. What does that even mean? What was the bottle neck in the first place?

    • Fatal Fridge

      Well maybe the key is that the service was *reimplemented* – whatever the technology you were using before, you tend to learn from your mistakes, drop legacy dead code, and fix your architecture or performance issues while reimplementing.

      • Dimitri

        I agree with you that changing the architecture has a lot to do with it. I would still like to understand how “page load” times were dropped by 50%. If someone is promoting a technology/architecture they need to provide the details.

        • http://encausse.net/ Jean-Philippe Encausse

          There is article on this subject (don’t have the link) in a nutshell NodeJS is full asynchronous without bottleneck (be carefull with database choice/driver)

          • Dimitri

            Sorry you are blindly repeating marketing trash. NodeJS uses an asynchronous event loop; this does not account for the misleading aspects of this article. The comparisons are questionable to say the least. As lots of other people have said here the key thing is that a new technical architecture has been developed and they have thrown away “technical debt”. I don’t think that NodeJS is bad it has its uses. However, it is is simply wrong to suggest that use of NodeJS has resulted or will result in all the benefits indicated in this article. It is fully possibly to write great and highly performant code on scalable architectures in a variety of languages.

          • http://encausse.net/ Jean-Philippe Encausse

            Dimitri, before blindly writing comments you could search on the web …

            Here is a link of a Java developers comparing NodeJS and Java and saying for given usecase NodeJS is better:


            It also explain in his blog Wwhy asynchronous code of NodeJS is better than Java NIO.

            In a nutshell it is because all the NodeJS stack is asynchronous, where Java because of it legacy have some bottleneck.

            Now on the other hand, cleary NodeJS is really young and people have to code things already done in Java for years.

          • Dimitri

            I am not blindly writing comments I am asking a question about what specifically nodejs provided here that explains the blog differences. I program in nodejs and several other languages fluentlly!

            I fully understand the value of Nodejs and understand exactly how it works. I even like it! The asynchronous event loop cannot be waved in a generic way to make the claims made here. Blindly repeating NodeJS is asynchronous does not help. If you do a bigger web search you will come across several blogs which question the numbers that are referred to in this blog.

            I am interested in the comments in this specific piece not on someones toy problem – i can manufacture many examples that can apparently show you NodeJS outperform Java. And they may or may not be relevant here. Btw the author, of the article you reference states very clearly that he is not trying to make a general statement. Back to this blog piece. Benchmarking is a complicated business.

            One can write asynchronously with several languages. The comment made by Fatal Bridge above is probably much nearer the mark. It would be very interesting to understand in the specific cases talked about here what the specific lessons and technical issues were without that this blog is simply a marketing document.

          • Dimitri

            I am not blindly writing comments. I am asking a question about what specifically nodejs provided here that explains the blog differences. I program in nodejs and several other languages fluentlly!

            Nodejs has value and I understand exactly how it works. I even like it! The asynchronous event loop cannot be waved in a generic way to make the claims made here. Blindly repeating NodeJS is asynchronous does not help. If you do a bigger web search you will come across several blogs which question the numbers that are referred to in this blog.

            I am interested in the comments in this specific blog piece not on someone’s toy problem. I can manufacture many examples that can apparently show you NodeJS outperform Java or something else. But they may or may not be relevant here. Btw the author of the article you reference states very clearly that he is not trying to make a general statement. Now, back to this blog piece. Benchmarking is a complicated business.

            One can write asynchronously with several languages. The comment made by Fatal Bridge above is probably much nearer the mark. It would be very interesting to understand in the specific cases talked about here what the specific technical issues were and what was learnt. Without that this blog is simply a marketing (and/or sales) document.

          • Jason

            It was the Groupon team who claimed their load times were reduced by 50%. That’s how they explained it:

            “Part of this is due to technology changes and part of this is because we had a chance to rewrite all of our web pages to be much slimmer. And we still expect to make significant gains here as we roll out additional changes.”

            Here’s the article: https://engineering.groupon.com/2013/misc/i-tier-dismantling-the-monoliths/

          • Colin Phillips

            languages can imitate asynchronous behaviours but it is not inherently async from it’s core up just as node can imitate sync behaviour as the other languages , sorry but just loosely saying you can write asynchronous code with other languages is half true , and their “asynchronous” performance sucks compared to node js , and if you understand that asynchronous architecture will always serve more clients faster then synchronous code you will start to see the real benefit of node

          • M.

            What utter rubbish. Async is async, and other languages have been doing it since callbacks became popular with C in the 70′s.

            Node’s “asynchronous architecture’ consists of a callback dispatch loop running in a single thread, which could be replicated by any competent programmer in any general purpose language that supports function pointers and|or delegates.

            But we don’t have to do that, because most modern languages already support asynchronous patterns baked right into their core language libraries, if not the language itself. C# (since 4.5) includes keywords that make the async pattern ridiculously easy to implement, (while still keeping synchronous syntax that is easier to grok) but it goes well beyond that also makes parallelizing work across the number of available cores a core part of it’s framework (since 4.0). Swift also has a very straightforward async pattern, and both would beat the living daylights out of some interpreted, dynamic dispatched language like JavaScript.

          • Colin Phillips

            You seem like u not getting why node is responds faster to more clients , yes a sync is not new but languages has been build to act synchronously which acts as a bottle neck for many request to a server and yet again their so called asynchronous libraries is build on a sync architecture and performance wise sucks against node is guess you just do not get it

          • M.

            Anybody that knows C# knows that Java is a crap language. So I don’t need an article telling me why I don’t want to use Java, I need an article that explains why node.js is better than *correctly* implemented C#.

            BTW, this “asynchronous event loop” everyone keeps talking about raises two nagging questions in my mind:

            1. Event driven programming was a 10 year rabbit hole for OOP. Modern designs (MVVM, MVC, REST) eschew it because it is un-testable, dependency entangled crap.

            2. You guys do realize that .net/mono (including C# and F#) have a number asynchronous, parallel extensions that were added to the language to help distribute non-blocking workload across multiple cores, right? We don’t have to spool up new processes to use another core, we get that built in if we know how to use the current feature set.

          • Anil Verma

            What??? C# better than Java.Heard about platform independence, open source and zillions of other things . Your above comment made my day friend. Too funny :).

          • M.

            Typical Java programmer who’s stuck in the 90′s. I write apps in Java, C# and Swift, I can tell you simply don’t comprehend just how badly Java lags behind. Java is “open-source” like Android is “linux”. Uh, no, it’s some committee driven crap run by IBM and other hopelessly dated commercial vendors defending their legacy product base.

            Not only is the vast majority of the .Net framework and C# language implementation available entirely in open source (see Mono), real .Net (branded by MS) is also largely open sourced, and C# runs on all three major OS platforms and the top three mobile platforms. (Java doesn’t) Several of the major framework components (OWIN and MVC5) are open sourced, and as for platform independence, show me a comparable Java technology to Xamarin for the mobile space, because Xamarin is architecturally way ahead of Apple’s Swift & objective C for native iOS development, and there’s a lot more of that development going on than people writing apps for Solaris or AIX.

            Java finally got lambda’s in version 8 (if you’re allowed to run that), so at least you don’t need to write those ponderous anonymous classes anymore.

            Generics in Java are utterly useless due to runtime type erasure, which prevents useful runtime type constraints like C#’s new(). When I see a generic method written in java that doesn’t use the pre generic technique of passing a Class parameter (C# calls it a “Type”), I think: “Here went a C# programmer, that hasn’t realized how useless Java’s generics are yet”.

            Reflection is also pretty weak, although not nearly as weak as Swift’s. Still, I’d take Swift’s support for generics over Java’s any day. Also, the lack of a var keyword is extra stupid, and maybe one day you’ll get an implementation of LINQ, built in support for asynchrony, extension methods, and distributing workload across multiple threads. Also, getting Java to admit they are stupid to eschew “syntactic sugar” and fix Calendar and String functions so we don’t have to keep adding DateUtils and StringUtils to every project is an obvious idea that just shows how much contempt the Java designers have for real world programmers, (and how little real world experience these designers have).

            Then all you need is to catch up in all the stuff invented for Java that has since been vastly improved in C#, such as DI frameworks, (Spring is ok, but there are many better choices in C#), Mocking (I’d take a powerful framework like Moq over an “easy” but weak framework like Mockito anyway), ORM’s (Java’s choices blow so bad that even EF is now vastly superior to Hibernate, and for microORM’s like Dapper? Why you’d need decent support for generics and actual extension methods for that, but the aristocrats that run Java don’t seem to think you guys deserve that sort of power. Java is the Chevrolet of programming languages, run by the GM of the 80′s.

          • Anil Verma

            FYI, link for you, just check who is rank 1 there (it is Java in case you don’t check out the link).


            C# is not a bad choice, but let’s not really compare it with Java.

            And below info is from a senior architect at Microsoft on what languages they use for various things. (Just check the open source section.)

            OS development (C/C++/C#/Assembler)

            Web Development (C#/VB-Dot-Net, ASP-Dot-Net, JavaScript)

            Compiler Development (Any targeted language via bootstrapping)

            Language Prototyping (any language)

            Research (F#/ …, Lisp/ …)

            Open Source Development (Java, JavaScript, …)

            I would like to know a billion dollar product company in 2015 which is .NET stack. (apart from Microsoft offcourse). I could name at least 10 such companies which run on JVM stack. Let’s not get married to languages and instead focus on solutions that come out of these languages. Merry Chirstmas M

          • Carlo Rizzante

            Node.js has at its core the V8 engine running on top of a C# application. So, basically, Node.js is C++ with a Javascript interface.


    • M.

      “What was the bottle neck in the first place?”
      For most shops, the answer would be the decidedly mediocre offshore Indian team the cranked out crappy code in a “safe” language. Trendy languages have an advantage in this regard: Offshore teams don’t do them because their customers aren’t asking for it yet.

      • Raj Kamal

        Okay, using a “safe” language, as you say, is a much wiser choice. after all languages come and go all the time. besides choice of programming language is dictated by requirements not customer. In any case, no developer in their right mind would ever use the *bleeding* edge technology( or trendy languages) for commercial application.

        • M.

          Millions of very good developers disagree. Better developers seek languages with better capabilities, and so they are familiar with technologies that offer features outside of mainstream demand, so they are early adopters of new frameworks that solve old problems better.

          FWIW, I think that node.js is a fad (similar to Angular) and is a poor choice for any complex project because they suffer from two major deficiencies: 1) Javascript as a language, while interesting, is and always will be crippled by dynamic typing, and 2) node.js punts every problem that can’t be async’d away.

  • Jason Young

    Was the traffic really that flat? It seems like there would be more variation in the chart provided. How many servers were being used?

  • https://jscrambler.com Pedro Fortuna

    And sometimes, enterprises will need to use JavaScript protection tools such as https://jscrambler.com

  • http://europa-antiqua-arca.blogspot.com/ clavdivs

    Nobody ever got fired for buying IBM. Still using COBOL and AS/400 here. I’m guessing this installation has seen a lot of trendy stuff come and go.

    • tomByrer

      > Nobody ever got fired for buying IBM

      You’re SOOO correct! http://www.ibm.com/developerworks/web/nodesdk/

    • Jason

      Iteration times with COBOL and mainframes take way too long for anyone to remember who bought what. They just don’t remember who to fire.

  • http://thinksafely.org Scott Dexter

    It’s easy to claim all these benefits when an emerging technology has the luxury of green-field and “let’s start this one from scratch” scenarios. Speed to market is driven as much by the amount of tech debt and legacy crapola than the latest wonderboy on the block.

    We had a similar scenario a while ago (perhaps too long for some of the very same node fanboys to be aware of): Classic ASP. VB on the backend, VB on the front end. What could go wrong?

    • Jason

      Actually, I know of a thousand success cases involving Classic ASP and VB clients. I know of a large brazilian bank that still uses this stack successfully, and a multinational mining company (probably the largest) still writing new stuff with it!

      Tech debt is the responsibility of the team. Yes, maintaining old tech is hard and expensive, but feasible (COBOL is the poster boy here). And it’s very common to see the same thing happening to older Java and C# apps, despite them being safe bets today. Heck, even C has problems with tech debt and maintainability, remember OpenSSL?

      And there’s another difference between Node and VB that should be accounted: Node.JS is open source and maintained by a community. Joyent has money in it but it’s not going away if they decide to drop it. VB on the other hand was closed source, proprietary, and Microsoft actually intended to kill it to give way for ASP.NET

      • M.

        A small point: Microsoft replaced an simplistic language designed to give more programmers access to COM functionality with a far more modern and capable framework that required significantly more technical skill to wield. In no sense were they trying to “kill” VB classic. VB6 was the best of the VB line by far (POBO data binding, implementation inheritance, etc) yet it was hopelessly behind what a modern memory managed language like C# could do, and those advantages have only mutliplied as C# has evolved to include capabilities from other programming paradigms like functional programming.

  • sebasporto

    It totally bothers me the title of your post “why .. is becoming the go-to technology …”, big assumption there: that node is becoming the go to tech. Yes, some big companies are using it, but many others are not and not even considering it. That title implies too much, feels like just marketing.

    • Jason

      Hence the “becoming”… And the phrase doesn’t imply that every company out there is firing the whole team to hire JS programmers and start rewriting their systems in another language.

      The point is that it’s on the radar right now. Even Microsoft and IBM have Node.JS offerings, and larger enterprises are beginning to feel safer about JS.

  • rsanchez1

    I love developing in node.js, but I can’t help but feel the developer picking between FB and PP was a little premature in his decision. Now FB is coming out with Hack, seeking to replace PHP, and the developer could have been at the forefront of yet another exciting new language.

  • juliusfoitzik

    I laughed when I read, that a re-write brought performance and loadtime improvements. I think this is not only due to the language but mainly due to the nature of a rewrite.

  • Rahul Chourasiya

    Thanks for such a valuable post. I understood its future scope in a well defined manner and have full faith about your given information.

  • prabhat sharma

    Hello Everybody! I’ve just started out on this wonderful journey in the field of software development. It’s been only a week.I’ll be working on C#.Please, guide me how I can plan the road ahead.Will be much appreciated.Thank You.

  • NTN

    Basically you’re saying that Node is better than PHP, which is not much. While not nearly as terrible as PHP, JS suffers from evolutionary development and being originally prototype-based.

    Try Golang. It is much harder to write incorrect code in it than in JS. Golang is designed to do the things that a programmer wants to do with minimum effort, rather than being elegant in theory. Unlike Node, it can use memory efficiently with arrays and structs. It is compiled but compilation is instant, unless you’re compiling a library with C code for the first time.

    In Go, you can write a web server in three lines of code using the standard library. In Go, there is cheap multithreading that I sometimes use even if I don’t need it because it’s so intuitive.

    And why write the client side in JS, when you can write it in Go and compile it to very efficient JS with GopherJS?

  • http://www.trawell.in Ramesh

    Looks like every big company adopted Node.js. Would like to know the conditions where Node.js is not suitable. Are there any case studies where Node.js actually failed to meet the purpose?