Node.js

Node.js is an open-source, cross-platform, JavaScript runtime environment (Framework) that executes JavaScript code outside a web browser. Node.js lets developers use JavaScript to write command line tools and for server-side scripting—running scripts server-side to produce dynamic web page content before the page is sent to the user's web browser. Consequently, Node.js represents a "JavaScript everywhere" paradigm,[6] unifying web-application development around a single programming language, rather than different languages for server- and client-side scripts.

Node.js
Original author(s)Ryan Dahl
Developer(s)Various
Initial releaseMay 27, 2009 (2009-05-27)[1]
Stable release
14.8.0 / August 11, 2020 (2020-08-11)[2]
Repository
Written inC, C++, JavaScript
Operating systemz/OS, Linux, macOS, Microsoft Windows, SmartOS, FreeBSD, OpenBSD, IBM AIX[3]
TypeRuntime environment
LicenseMIT license[4][5]
Websitenodejs.org 

Though .js is the standard filename extension for JavaScript code, the name "Node.js" doesn't refer to a particular file in this context and is merely the name of the product. 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).[7]

The Node.js distributed development project was previously governed by the Node.js Foundation,[8] and has now merged with the JS Foundation to form the OpenJS Foundation, which is facilitated by the Linux Foundation's Collaborative Projects program.[9]

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

History
Ryan Dahl, creator of Node.js, in 2010

Node.js was written initially by Ryan Dahl in 2009,[24] about thirteen years after the introduction of the first server-side JavaScript environment, Netscape's LiveWire Pro Web.[25] The initial release supported only Linux and Mac OS X. Its development and maintenance was led by Dahl and later sponsored by Joyent.[26]

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.[27]

Dahl demonstrated the project at the inaugural European JSConf on 8 November 2009.[28][29][30] Node.js combined Google's V8 JavaScript engine, an event loop, and a low-level I/O API.[31]

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

In June 2011, Microsoft and Joyent implemented a native Windows version of Node.js.[33] 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.[34] In January 2014, Schlueter announced that Timothy J. Fontaine would lead the project.[35]

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.[36][37] Unlike Node.js,[38] the authors planned to keep io.js up-to-date with the latest releases of the Google V8 JavaScript engine.[39]

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.[40]

In September 2015, Node.js v0.12 and io.js v3.3 were merged back together into Node v4.0.[41] This merge brought V8 ES6 features into Node.js and a long-term support release cycle.[42] 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 merge.[43]

In 2019, the JS Foundation and Node.js Foundation merged to form the OpenJS Foundation.

Overview

Node.js allows the creation of Web servers and networking tools using JavaScript and a collection of "modules" that handle various core functionalities.[28][31][44][45][46] 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.[31][45][47] Node.js's modules use an API designed to reduce the complexity of writing server applications.[31][45]

JavaScript is the only language that Node.js supports natively, but many compile-to-JS languages are available.[48] As a result, Node.js applications can be written in CoffeeScript,[49] Dart, TypeScript, ClojureScript and others.

Node.js is primarily used to build network programs such as Web servers.[44] The most significant difference between Node.js and PHP is that most functions in PHP block until completion (commands only execute after previous commands finish), while Node.js functions are non-blocking (commands execute concurrently or even in parallel,[50][51] and use callbacks to signal completion or failure).[44]

Node.js is officially supported on Linux, macOS and Microsoft Windows 8.1 and Server 2012 (and later),[3] with tier 2 support for SmartOS and IBM AIX and experimental support for FreeBSD. OpenBSD also works, and LTS versions available for IBM i (AS/400).[52] The provided source code may also be built on similar operating systems to those officially supported or be modified by third parties to support others such as NonStop OS[53] and Unix servers.

Platform architecture

Node.js brings event-driven programming to web servers, enabling development of fast web servers in JavaScript.[31] Developers can create scalable servers without using threading, by using a simplified model of event-driven programming that uses callbacks to signal the completion of a task.[31] Node.js connects the ease of a scripting language (JavaScript) with the power of Unix network programming.[31]

Node.js was built on the Google V8 JavaScript engine since it was open-sourced under the BSD license. It is proficient with internet fundamentals such as HTTP, DNS, TCP.[28] JavaScript was also a well-known language, making Node.js accessible to the web development community.[28]

Industry support

There are 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 are multiple developer conferences and events that support the Node.js community, including NodeConf, Node Interactive, and Node Summit as well as a number of regional events.

The open-source community has developed web frameworks to accelerate the development of applications. Such frameworks include Connect, Express.js, Socket.IO, Feathers.js, Koa.js, Hapi.js, Sails.js, Meteor, Derby, and many others.[31][54] Various packages have also been created for interfacing with other languages or runtime environments such as Microsoft .NET.[55]

Modern desktop IDEs provide editing and debugging features specifically for Node.js applications. Such IDEs include Atom, Brackets, JetBrains WebStorm,[56][57] Microsoft Visual Studio (with Node.js Tools for Visual Studio,[58] or TypeScript with Node definitions,[59][60][61][62]) NetBeans,[63] Nodeclipse Enide Studio[64] (Eclipse-based), and Visual Studio Code.[65][66] Certain online web-based IDEs also support Node.js, such as Codeanywhere, Codenvy, Cloud9 IDE, Koding, and the visual flow editor in Node-RED.

Node.js is supported across a number of cloud hosting platforms like Jelastic, Google Cloud Platform, AWS Elastic Beanstalk, Joyent and others.

Releases
Release Status Code name Release date Active LTS start Maintenance start Maintenance end
Old version, no longer maintained: v0.10.x Old version, no longer maintained: End-of-Life 2013-03-11 - 2015-10-01 2016-10-31
Old version, no longer maintained: v0.12.x Old version, no longer maintained: End-of-Life 2015-02-06 - 2016-04-01 2016-12-31
Old version, no longer maintained: 4.x Old version, no longer maintained: End-of-Life Argon[67] 2015-09-08 2015-10-01 2017-04-01 2018-04-30
Old version, no longer maintained: 5.x Old version, no longer maintained: End-of-Life 2015-10-29 N/A 2016-06-30
Old version, no longer maintained: 6.x Old version, no longer maintained: End-of-Life Boron[67] 2016-04-26 2016-10-18 2018-04-30 2019-04-30
Old version, no longer maintained: 7.x Old version, no longer maintained: End-of-Life 2016-10-25 N/A 2017-06-30
Old version, no longer maintained: 8.x Old version, no longer maintained: End-of-Life Carbon[67] 2017-05-30 2017-10-31 2019-01-01[68] 2019-12-31
Old version, no longer maintained: 9.x Old version, no longer maintained: End-of-Life 2017-10-01 N/A 2018-06-30
Older version, yet still maintained: 10.x Older version, yet still maintained: Maintenance LTS Dubnium[67] 2018-04-24 2018-10-30 2020-05-19 2021-04-01
Old version, no longer maintained: 11.x Old version, no longer maintained: End-of-Life 2018-10-23 N/A 2019-06-01
Older version, yet still maintained: 12.x Older version, yet still maintained: Active LTS Erbium[67] 2019-04-23 2019-10-22 2020-10-20 2022-04-01
Old version, no longer maintained: 13.x Old version, no longer maintained: End-of-Life 2019-10-22 N/A 2020-04-01 2020-06-01
Current stable version: 14.x Current stable version: Current Fermium[67] 2020-04-21 2020-10-20 2021-10-20 2023-04-30
Future release: 15.x Future release: Pending 2020-10-20 N/A 2021-04-01 2021-06-01
Future release: 16.x Future release: Pending Gallium[67] 2021-04-20 2021-10-26 2022-10-18 2024-04-30
Legend:
Old version
Older version, still maintained
Latest version
Latest preview version
Future release

New major releases of Node.js are cut from the GitHub master branch every six months. Even-numbered versions are cut in April and odd-numbered versions are cut in October. When a new odd version is released, the previous even version undergoes transition to Long Term Support (LTS), which gives that version 18 months of active support from the date it is designated LTS. After these 18 months expire, an LTS release receives an additional 12 months of maintenance support. An active version receives non-breaking backports of changes a few weeks after they land in the current release. A maintenance release only receives critical fixes and documentation updates.[67] The LTS Working Group manages strategy and policy in collaboration with the Technical Steering Committee of the Node.js Foundation.

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 event loop, using non-blocking I/O calls, allowing it to support tens of thousands of concurrent connections without incurring the cost of thread context switching.[69] The design of sharing a single thread among all the requests that use the observer pattern is intended for building highly concurrent applications, where any function performing I/O must use a callback. To accommodate the single-threaded event loop, Node.js uses the libuv library—which, in turn, uses a fixed-sized thread pool that handles some of the non-blocking asynchronous I/O operations.[7]

A thread pool handles the execution of parallel tasks in Node.js. The main thread function call posts tasks to the shared task queue, which threads in the thread pool pull and execute. Inherently non-blocking system functions such as networking translate to kernel-side non-blocking sockets, while inherently blocking system functions such as file I/O run in a blocking way on their own threads. When a thread in the thread pool completes a task, it informs the main thread of this, which in turn, wakes up and executes the registered callback.

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,[50] StrongLoop Process Manager,[70] or pm2.[71] However, developers can increase the default number of threads in the libuv thread pool. The server operating system (OS) is likely to distribute these threads across multiple cores.[72] Another problem is that long-lasting computations and other CPU-bound tasks freeze the entire event-loop until completion.

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 such as 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.

V8

V8 is the JavaScript execution engine which was initially built for Google Chrome. It was then open-sourced by Google in 2008. Written in C++, V8 compiles JavaScript source code to native machine code at runtime. [7] As of 2016, it also includes Ignition, a bytecode interpreter.

Package management

npm is the pre-installed package manager for the Node.js server platform. It installs Node.js programs from the npm registry, organizing the installation and management of third-party Node.js programs. Packages in the npm registry can range from simple helper libraries such as Lodash to task runners such as Grunt.

Unified API

Node.js can be combined with a browser, a database that supports JSON data (such as Postgres,[73] MongoDB, or CouchDB) and JSON for a unified JavaScript development stack. With the adaptation of what were essentially server-side development patterns such as 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 with the operating system so the OS notifies it of connections and issues 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.[74] 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.

WebAssembly

Node.js supports WebAssembly and as of version 14.x has an experimental support of WASI, the WebAssembly System Interface.

Project governance

In 2015, various branches of the greater Node.js community began working under the vendor-neutral Node.js Foundation. The stated purpose of the organization "is to enable widespread adoption and help accelerate development of Node.js and other related modules through an open governance model that encourages participation, technical contribution, and a framework for long-term stewardship by an ecosystem invested in Node.js' success."[75]

The Node.js Foundation Technical Steering Committee (TSC) is the technical governing body of the Node.js Foundation. The TSC is responsible for the core Node.js repo as well as dependent and adjacent projects. Generally the TSC delegates the administration of these projects to working groups or committees.[76] The LTS group that manages long term supported releases is one such group. Other current groups include Website, Streams, Build, Diagnostics, i18n, Evangelism, Docker, Addon API, Benchmarking, Post-mortem, Intl, Documentation, and Testing.[77]

In August 2017, a third of the TSC members resigned due to a dispute related to the project's code of conduct.[78]

gollark: Huh. Apparently New Zealand just declared itself free of COVID-19.
gollark: ++delete ø
gollark: æÆæÆ
gollark: OH NOGITHUBIS BEES
gollark: Some users were weirdly attached to it, I had to add a switch.

See also

References
  1. "node-v0.x-archive on GitHub". Retrieved 2 August 2014.
  2. "Node.js 14 ChangeLog". Retrieved 11 August 2020 – via GitHub.
  3. "nodejs/node". GitHub.
  4. "node/LICENSE at master". GitHub. Node.js Foundation. 17 September 2018. Retrieved 17 September 2018.
  5. "The MIT License". Open Source Initiative. 17 September 2018. Retrieved 17 September 2018.
  6. gcuomo (24 October 2013). "JavaScript Everywhere and the Three Amigos (Into the wild BLUE yonder!)". www.ibm.com.
  7. Laurent Orsini (7 November 2013). "What You Need To Know About Node.js". readwrite. Archived from the original on 7 November 2013. Retrieved 22 January 2016.
  8. "Node.js Foundation - Node.js". Retrieved 4 July 2015.
  9. "Linux Foundation Collaborative Projects". Retrieved 4 July 2015.
  10. Why GoDaddy's Nodejitsu deal is great for Node.js, VentureBeat, 10 February 2015
  11. Geitgey, Adam (30 October 2013). "I-Tier: Dismantling the Monoliths". Groupon. Retrieved 30 April 2014.
  12. "IBM Bluemix". Retrieved 4 July 2015.
  13. "You'll never believe how LinkedIn built its new iPad app". VentureBeat. 2 May 2012. Retrieved 10 May 2012.
  14. "Blazing fast node.js: 10 performance tips from LinkedIn Mobile". Retrieved 7 April 2015.
  15. Baxter-Reynolds, Matthew (9 November 2011). "Here's why you should be happy that Microsoft is embracing Node.js". London: The Guardian. Retrieved 10 May 2012.
  16. "WebMatrix - Front End Web Developers take note (ASP.NET, PHP, node.js and more)". Retrieved 2 August 2014.
  17. Node.js in Flames 19 November 2014
  18. "Clash of the Titans: Releasing the Kraken, NodeJS @paypal". fluentconf.com. 28 May 2013. Retrieved 11 September 2013.
  19. "All such companies and their products in which Node.js is used". Retrieved 2 August 2014.
  20. "SAP AppBuilder". SAP. 10 March 2014. Archived from the original on 12 February 2014. Retrieved 10 October 2018.
  21. The Node Ahead: JavaScript leaps from browser into future, The Register, 1 March 2011
  22. "Why Walmart is using Node.js". VentureBeat. 24 January 2012. Retrieved 10 May 2012.
  23. "Why You Really Need (A) node.js development services". codebrahma. 10 January 2018. Retrieved 10 January 2018.
  24. "About Node.js, and why you should add Node.js to your skill set?". Training.com. Training.com. Retrieved 23 October 2016.
  25. "Netscape opens intranet attack". CNET. Retrieved 20 April 2017.
  26. Ryan Dahl (9 November 2010). "Joyent and Node". Google Groups. Retrieved 5 February 2015.
  27. "PHP 7 vs Node.js? They Can Be Partners, Not Competitors For a Developer!". Retrieved 21 December 2016.
  28. Sams Teach Yourself Node.js in 24 Hours, Sams Publishing, 05-Sep-2012
  29. "Ryan Dahl at JSConf EU 2009".
  30. "Ryan Dahl at JSConf EU 2009 Video".
  31. Professional Node.js: Building JavaScript Based Scalable Software, John Wiley & Sons, 01-Oct-2012
  32. "Earliest releases of npm". GitHub. Retrieved 27 July 2016.
  33. "Porting Node to Windows With Microsoft's Help". Retrieved 17 April 2016.
  34. Dahl, Ryan. "New gatekeeper". Retrieved 26 October 2013.
  35. Schlueter, Isaac (15 January 2014). "The Next Phase of Node.js". Retrieved 21 January 2014.
  36. Krill, Paul (4 December 2014). "Why io.js Decided to Fork Node.js". JavaWorld. Retrieved 15 December 2014.
  37. Q&A: Why io.js decided to fork Node.js, InfoWorld Tech Watch
  38. Ben Noordhuis (12 November 2014). "Issue 3692: function suddenly becomes undefined". V8 JavaScript Engine Issues. Retrieved 2 February 2015.
  39. Mikeal, Rogers (28 January 2015). "State of io.js". Retrieved 2 February 2015.
  40. "Node.js Foundation Advances Community Collaboration, Announces New Members and Ratified Technical Governance". Archived from the original on 24 June 2015. Retrieved 4 July 2015.
  41. "Node.js Foundation Combines Node.js and io.js Into Single Codebase in New Release". Retrieved 28 January 2016.
  42. "io.js and Node.js merge". Retrieved 27 June 2015.
  43. Io.js, JavaScript I/O, "io.js has merged with the Node.js project again. There won't be any further io.js releases. All of the features in io.js are available in Node.js v4 and above."
  44. Node.js for PHP Developers, O'Reilly Media, Inc., 2013
  45. Node.js Essentials, Packt Publishing, 10-Nov-2015
  46. Smashing Node.js: JavaScript Everywhere, John Wiley & Sons, 14-Aug-2012
  47. Modules, Nodejs Website
  48. "List of languages that compile to JS". Github.
  49. CoffeeScript on Node.js. O'Reilly Media, Inc. 15 April 2013. ISBN 9781449316846. Retrieved 17 May 2015.
  50. "Node.js's cluster module". Retrieved 19 October 2017.
  51. "Node.js's child_process module". Retrieved 19 October 2017.
  52. Foundation, Node js. "Installing Node.js via package manager". Node.js. Retrieved 19 May 2019.
  53. "bomBora - Node.js for NonStop". Infrasoft. Retrieved 14 August 2015.
  54. Express.js Guide: The Comprehensive Book on Express.js, Azat Mardan, 28-May-2014
  55. Edge.js bridges the gap between Node.js and .NET, TechRepublic, Tony Patton, 1 July 2014
  56. Node.js, WebStorm supports integration with the Node.js runtime environment, WebStorm Help
  57. Running and Debugging Node.js, WebStorm Help
  58. "Node.js Tools for Visual Studio". Retrieved 1 February 2016.
  59. soywiz/typescript-node-definitions TypeScript's typings for some popular node.js modules, GitHub
  60. DefinitelyTyped, GitHub
  61. The repository for high quality TypeScript type definitions Archived 3 February 2016 at the Wayback Machine
  62. ImageBoard, A Node.js + Express + MongoDB application built using TypeScript on the server, TypeScript Samples
  63. Krill, Paul (10 November 2015). "Node.js takes center stage in NetBeans 8.1". InfoWorld.
  64. Nodeclipse, Enide -- Node.JS development in Eclipse, Nodeclipse Website
  65. Hello Visual Studio Code (with NodeJS), Channel 9, Microsoft
  66. Node.js Applications with VS Code, Visual Studio Code
  67. "nodejs/Release". GitHub. Retrieved 3 May 2018.
  68. "Node 8 reschedule". Retrieved 22 January 2019.
  69. "Node.js w/1M concurrent connections!". caustik's blog.
  70. "StrongLoop Process Manager".
  71. "GitHub - Unitech/pm2: Production process manager for Node.js applications with a built-in load balancer". GitHub.
  72. Aleksander Kasiuk (22 April 2015). "On problems with threads in node.js - Future Processing".
  73. "PostgreSQL: Documentation: 9.4: JSON Types". www.postgresql.org. Retrieved 20 October 2016.
  74. About Node.js, Node.js Website
  75. Foundation, Node.js. "Node.js Foundation | Node.js". nodejs.org. Retrieved 8 March 2017.
  76. "nodejs/TSC". GitHub. Retrieved 8 March 2017.
  77. Foundation, Node.js. "Working Groups | Node.js". nodejs.org. Retrieved 8 March 2017.
  78. Whittaker, Zack, After governance breakdown, Node.js leaders fight for its survival, ZDNet, 25 August 2017

Further reading
  • Hughes-Croucher, Tom; Wilson, Mike (April 2012), Up and Running with Node.js, O'Reilly Media, ISBN 978-1-4493-9858-3
  • Ornbo, George (September 2012), Sams Teach Yourself Node.js in 24 Hours, SAMS Publishing, ISBN 978-0-672-33595-2
  • Teixeira, Pedro (October 2012), Professional Node.js, John Wiley & Sons, ISBN 978-1-118-22754-1
  • Randal L. Schwartz and Aaron Newcomb (9 January 2013). "Episode 237: Node.js". twit.tv/show/floss-weekly (Podcast). TWiT.tv. Event occurs at 1:08:13. Retrieved 9 January 2013.
  • Gackenheimer, Cory (October 2013), Node.js Recipes: A Problem-Solution Approach, Apress, ISBN 978-1-4302-6058-5

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.