10 Companies Who Switched to Node.js – Is Node.js The Future of Web?
Node.js has an event-driven architecture capable of asynchronous I/O. These design choices aim to optimize throughput and scalability in Web applications with many input/output operations, as well as for real-time Web applications (e.g., real-time communication programs and browser games).
Node.js was developed by Ryan Dahl, an American freelance developer living in Germany. Ryan developed Node.js in the unfortunate, yet extra motivational, ‘starving artist’ era in his career.
Node.js did not get the recognition it truly deserved until Ryan gained the attention of Joyent, a company who has since been acquired by Samsung. Joyent provided Ryan with the resources necessary to prove his concept with Node.js, as well as get him on their payroll to get on his feet again – and the rest is history.
Ryan Paul has written an excellent behind-the-scenes look at LinkedIn’s mobile engineering. While the mobile part of the story–23% mobile usage; focus on simplicity, ease of use, and reliability; using a room metaphor; 30% native, 80% HTML; embedded lightweight HTTP server; single client-app connection–could help guide your mobile strategy, the backend effects of moving from Rails to Node.js may also prove interesting.
After evaluation, some of the advantages of Node.js were:
- Much better performance and lower memory overhead than other tested options, running up to 20x faster in some scenarios
- Frontend and backend mobile teams could be combined into a single unit.
- Servers were cut to 3 from 30. Enough headroom remains to handle 10x current levels of resource utilization.
- Development could focus more on application development than firefighting
Clearly a lot of issues are being mixed together here. We have a rewrite, a change of stack, and a change of logic distribution between the server and the client, so there’s plenty of room to argue where the gains really came from, but it’s clear LinkedIn believes the use of Node.js was a big win for them.
9. Capital ONE
An excerpt from an interview with Azat Mardan, a Developer for Capital One.
We have over 5,000 engineers and different teams who started using Node.js at different times. Right now, I think a few of our most popular use cases and examples would be Hygieia, which is an open-source dashboard for DevOps. It started in 2013 and we announced it last year at OSCON. As of yesterday, it has about 900 GitHub stars; I was surprised to see that, so that’s doing pretty well. We’re using Node.js for the frontend and for the build too, for that project.
Traditionally, Netflix has been an enterprise Java shop, but “as we migrated out of the data center to the cloud we moved to a more service-based architecture,” Trott said. The company is in the process of breaking up what used to be a monolithic Java application into a set of smaller services. Java still powers the backend of Netflix, but all the stuff that the user sees comes from Node.
Microsoft is very active in the progression of Node.js, they are also a foundation member. Microsoft also has their own fork of Node.js’s engine, ChakraCore. This project is still under development.
2. eBay & PayPal
1. Google & YouTube