Node.js

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).^[5]

The Node.js distributed development project, governed by the Node.js Foundation,^[6] is facilitated by the Linux Foundation‘s Collaborative Projects program.^[7]

Corporate users of Node.js software include GoDaddy,^[8]Groupon,^[9]IBM,^[10]LinkedIn,^[11][12]Microsoft,^[13][14]Netflix,^[15]PayPal,^[16][17]Rakuten, SAP,^[18]Voxer,^[19]Walmart,^[20]Yahoo!,^[21] and Cisco Systems.

History

Node.js was originally written in 2009 by Ryan Dahl.^[22] The initial release supported only Linux. Its development and maintenance was led by Dahl and later sponsored by Joyent.^[23]

Dahl was inspired to create Node.js after seeing a file upload progress bar on Flickr. The browser did not know how much of the file had been uploaded and had to query the Web server. Dahl desired an easier way.^[5][24]

Dahl criticized the limited possibilities of the most popular web server in 2009, Apache HTTP Server, to handle a lot of concurrent connections (up to 10,000 and more) and the most common way of creating code (sequential programming), when code either blocked the entire process or implied multiple execution stacks in the case of simultaneous connections. ^[25]

Dahl demonstrated the project at the inaugural European JSConf on November 8, 2009.^[26][27][28] Node.js combined Google‘s V8 JavaScript engine, an event loop and a low-level I/O API.^[29] The project received a standing ovation.^[30]

In January 2010, a package manager was introduced for the Node.js environment called npm.^[31] The package manager makes it easier for programmers to publish and share source code of Node.js libraries and is designed to simplify installation, updating and uninstallation of libraries.^[29]

In June 2011, Microsoft and Joyent implemented a native Windows version of Node.js.^[32] The first Node.js build supporting Windows was released in July 2011.

In January 2012, Dahl stepped aside, promoting coworker and npm creator Isaac Schlueter to manage the project.^[33] In January 2014, Schlueter announced that Timothy J. Fontaine would lead the project.^[34]

In December 2014, Fedor Indutny started io.js, a fork of Node.js. Due to the internal conflict over Joyent’s governance, io.js was created as an open governance alternative with a separate technical committee.^[35][36] Unlike Node.js,^[37] the authors planned to keep io.js up-to-date with the latest releases of the Google V8 JavaScript engine.^[38]

In February 2015, the intent to form a neutral Node.js Foundation was announced. By June 2015, the Node.js and io.js communities voted to work together under the Node.js Foundation.^[39]

In September 2015, Node.js v0.12 and io.js v3.3 were merged back together into Node v4.0.^[40] This brought V8 ES6 features into Node.js, and a long-term support release cycle.^[41] As of 2016, the io.js website recommends that developers switch back to Node.js and that no further releases of io.js are planned due to the merger.^[42]

Overview

Node.js allows the creation of Web servers and networking tools using JavaScript and a collection of “modules” that handle various core functionality.^{[26][29][43][44][45]} Modules are provided for file system I/O, networking (DNS, HTTP, TCP, TLS/SSL, or UDP), binary data (buffers), cryptography functions, data streams and other core functions.^[29][44][46] Node.js’s modules use an API designed to reduce the complexity of writing server applications.^[29][44]

Node.js applications can run on macOS, Microsoft Windows, NonStop,^[47] and Unix servers. They can alternatively be written with CoffeeScript^[48] (a JavaScript alternative), Dart or Microsoft TypeScript (strongly typed forms of JavaScript), or any other language that can compile to JavaScript.^[48]

Node.js is primarily used to build network programs such as Web servers.^[43] The biggest difference between Node.js and PHP is that most functions in PHP block until completion (commands execute only after previous commands have completed), while functions in Node.js are designed to be non-blocking (commands execute in parallel, and use callbacks to signal completion or failure).^[43]

Platform architecture

Node.js brings event-driven programming to web servers, enabling development of fast web servers in JavaScript.^[29] Developers can create highly scalable servers without using threading, by using a simplified model of event-driven programming that uses callbacks to signal the completion of a task.^[29] Node.js was created because concurrency is difficult in many server-side programming languages, and often leads to poor performance.^[26] Node.js connects the ease of a scripting language (JavaScript) with the power of Unix network programming.^[29]

Node.js was built on the Google V8 JavaScript engine since it was open-source under the BSD license, extremely fast, and proficient with internet fundamentals like HTTP, DNS, TCP.^[26] Also, JavaScript was a well-known language, making Node.js immediately accessible to the entire web development community.^[26]

Industry support

People have built thousands of open-source libraries for Node.js – most of them hosted on the npm website. The Node.js developer community has two main mailing lists and the IRC channel #node.js on freenode. There is an annual Node.js developer conference, called NodeConf.^[49]

The open-source community has developed server frameworks to accelerate the development of applications. Such frameworks include Connect, Express.js, Socket.IO, Koa.js, Hapi.js, Sails.js, Meteor, Derby, and many others.^[29][50]

Modern desktop IDEs provide editing and debugging features specifically for Node.js applications. Such IDEs include Atom, Brackets, JetBrains WebStorm,^[51][52]Microsoft Visual Studio (with Node.js Tools for Visual Studio,^[53] or TypeScript with Node definitions^{[54][55][56][57]}), NetBeans,^[58]Nodeclipse Enide Studio^[59] (Eclipse-based) and Visual Studio Code.^[60][61] Certain online web-based IDEs also support Node.js, such as Codeanywhere, Codenvy, Cloud9 IDE and Koding.

Technical details

Node.js is a Javascript runtime environment that processes incoming requests in a loop, called the event loop.

Threading

Node.js operates on a single thread, using non-blocking I/O calls, allowing it to support tens of thousands of concurrent connections without incurring the cost of thread context switching.^[63] The design of sharing a single thread between all the requests that uses the observer pattern is intended for building highly concurrent applications, where any function performing I/O must use a callback. In order to accommodate the single-threaded event loop, Node.js utilizes the libuv library that in turn uses a fixed-sized threadpool that is responsible for some of the non-blocking asynchronous I/O operations.^[5]

A downside of this single-threaded approach is that Node.js doesn’t allow vertical scaling by increasing the number of CPU cores of the machine it is running on without using an additional module, such as cluster,^[64] StrongLoop Process Manager^[65] or pm2.^[66] However, developers can increase the default number of threads in the libuv threadpool; these threads are likely to be distributed across multiple cores by the server operating system.^[67]

Execution of parallel tasks in Node.js is handled by a thread pool. The main thread call functions post tasks to the shared task queue that threads in the thread pool pull and execute. Inherently non-blocking system functions like networking translates to kernel-side non-blocking sockets, while inherently blocking system functions like file I/O run in a blocking way on its own thread. When a thread in the thread pool completes a task, it informs the main thread of this that in turn wakes up and execute the registered callback. Since callbacks are handled in serial on the main thread, long lasting computations and other CPU-bound tasks will freeze the entire event-loop until completion.

V8[edit]

V8 is the JavaScript execution engine built for Google Chrome and open-sourced by Google in 2008. Written in C++, V8 compiles JavaScript source code to native machine code instead of interpreting it in real time.^[5]

Node.js uses libuv to handle asynchronous events. Libuv is an abstraction layer for network and file system functionality on both Windows and POSIX-based systems like Linux, macOS, OSS on NonStop and Unix.

The core functionality of Node.js resides in a JavaScript library. The Node.js bindings, written in C++, connect these technologies to each other and to the operating system.

Package management

npm is the pre-installed package manager for the Node.js server platform. It is used to install Node.js programs from the npm registry, organizing the installation and management of third-party Node.js programs. npm is not to be confused with the CommonJS require() statement. It is not used to load code; instead, it is used to install code and manage code dependencies from the command line. The packages found in the npm registry can range from simple helper libraries like Underscore.js to task runners like Grunt.^[68]

Unified API

Node.js can be combined with a browser, a database supporting JSON data (such as Postgres,^[69]MongoDB or CouchDB) and JSON for a unified JavaScript development stack. With the adaptation of what were essentially server-side development patterns like MVC, MVP, MVVM, etc., Node.js allows the reuse of the same model and service interface between client-side and server-side.

Event loop

Node.js registers itself with the operating system so that it is notified when a connection is made, and the operating system will issue a callback. Within the Node.js runtime, each connection is a small heap allocation. Traditionally, relatively heavyweight OS processes or threads handled each connection. Node.js uses an event loop for scalability, instead of processes or threads.^[70] In contrast to other event-driven servers, Node.js’s event loop does not need to be called explicitly. Instead callbacks are defined, and the server automatically enters the event loop at the end of the callback definition. Node.js exits the event loop when there are no further callbacks to be performed.

Alternatives

JXcore

JXcore is a fork of Node.js targeting mobile devices and IoTs. Its first beta was released in January 2014. It was open sourced^[71] on February 13, 2015 and made available through a GitHub repository.^[72] JXcore can use either of the Google V8 or Mozilla SpiderMonkey JavaScript engines. As a result, JXcore can run Node applications on iOS devices using SpiderMonkey. As of March 25, 2016, active development on JXcore has been halted.^[73]

Other languages

Similar open source event-driven server frameworks for other platforms include:

Node.js may utilize code written in other programming languages using:

• Edge.js allows Microsoft .NET applications to run Node.js scripts in-process, and allows Node.js servers to utilize .NET compiled code via async callbacks.^[74][75][76]
• Luvit implements the Node.js APIs for the language Lua^[77]
• Node-julia allows using Julia with Node.js/io.js
• The COBOL bridge for Node.js allows using COBOL with Node.js^[78]