Recently, Microsoft has really embraced NodeJS, thoroughly supporting Node on the Azure cloud platform. It's one of Azure’s major features and they’ve integrated Visual Studio support for Node. Microsoft has also developed a version of Node for Internet Of Things (IoT) applications, which is great because it’s lightweight and efficient.
The NodeJS version worked out so well that they chose to use it in production and build all client-facing applications in Node going forward. That means that most of what you see in your account is running on Node.
PayPal even went as far as to create and maintain their own version of Express, called KrakenJS!
Over time, Netflix moved away from its more traditional structure into the cloud and started to introduce NodeJS. With NodeJS, Netflix was able to break down pieces of their user interface into individual services.
This more distributed approach was able to speed things up and alleviate stress on their servers and today, a large portion of Netflix’s interface is running on Node.
Groupon used to be infamously slow. Why? They were powered by Ruby on Rails. That’s the same framework that brought you the Twitter fail whale: Groupon was all one gigantic Ruby on Rails application:
Thanks to difficulties in speed and maintainability, they decided to change over to NodeJS.
Node allowed Groupon to rebuild their entire US website by breaking down everything into individual NodeJS web applications.
Groupon is now made up of over 20 Node applications and it moves much faster as a whole.
Groupon is currently moving all of their international sites to NodeJS and has joined the NodeJS Foundation.
Uber needs to handle loads of data in real time; they receive millions of simultaneous requests, and that’s not just hits on a page. Uber needs to track driver locations, rider locations, and incoming ride requests. It has to seamlessly sort that data and match riders as fast as possible:
Node is designed to handle requests and hand off data quickly; its asynchronous capabilities are a huge part of that.
Node is central to Uber’s user-facing stack for just that reason.
Facebook created React, one of the most popular front end frameworks. Facebook uses React on Facebook.com, as well as Instagram and WhatsApp.
Node worked so well that eBay not only kept using it for that particular service, but also began migrating their entire user-facing stack to NodeJS.
Just about everything that you interact with on eBay is powered by Node.
Most people probably don’t think of Walmart as a tech company, but because they’re one of the largest retailers in the world, their online retail business is gigantic. It’s not much of a stretch to understand how they need to build a technologically advanced web application to drive their online business:
However, Walmart needed something faster and lighter weight for their mobile site. So, they turned to NodeJS.
NodeJS was also the ideal choice for other web applications within their marketplace that require multiple users to be able to access management interfaces simultaneously.
LinkedIn relies on NodeJS for its mobile site and a few years back, LinkedIn used Rails for its mobile site. As with other large Rails applications, it was slow, monolithic, and it scaled poorly:
LinkedIn switched over to NodeJS to solve its scaling problems.
Node’s asynchronous capabilities allowed the LinkedIn mobile site to perform more quickly than before while using fewer resources.
Node also made data sharing and building APIs easier for the LinkedIn developers.