How does JavaScipt work?
- Loading new content or data onto the page without reloading the page
- Rollover effects and dropdown menus
- Animating page elements such as fading, resizing or relocating
- Playing audio and video
- Validating input from Webforms
- Repairing browser compatibility issues
Take a search engine for example. Today, search engines almost all have an autocomplete function. The user begins typing a word into the search box and a list of possible search terms or phrases appears below. The experience is seamless. Suggested search terms appear without reloading the page.
Recently, Microsoft has really embraced NodeJS. They thoroughly support 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. NodeJS is great for IoT because it’s lightweight and efficient.
The online payment giant was one of the earliest adopters of NodeJS. During an overhaul of their account overview page, they decided to try building the page in Node at the same time as their usual Java development. 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.
Like PayPal, Netflix started out using Java for just about everything. They too ran into problems with Java’s size and the time it required to develop.
Over time, Netflix moved away from its more traditional structure into the cloud and started to introduce NodeJS. With Node, 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. Today, a large portion of Netflix’s interface is running on Node.
It doesn’t stop there. Facebook created React, one of the most popular front-end frameworks. Facebook uses React on Facebook.com as well as Instagram and WhatsApp.
LinkedIn relies on NodeJS for its mobile site. 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 LinkedIn developers.