{"id":2706,"date":"2013-05-10T22:18:41","date_gmt":"2013-05-11T02:18:41","guid":{"rendered":"https:\/\/www.inmotionhosting.com\/support\/2013\/05\/10\/nodejs\/"},"modified":"2025-11-17T15:09:44","modified_gmt":"2025-11-17T20:09:44","slug":"nodejs","status":"publish","type":"post","link":"https:\/\/www.inmotionhosting.com\/support\/website\/nodejs\/","title":{"rendered":"What is Node.js?"},"content":{"rendered":"\n

Node.js<\/strong> is a popular server-side JavaScript framework built off the impressively fast open source V8 JavaScript engine used in Google Chrome. Programs for Node.js<\/strong> are written in JavaScript using event-driven, asynchronous I\/O requests which can help allow for handling of tens of thousands of simultaneous client connections efficiently.<\/p>\n\n\n\n

Node.js<\/strong> is built around a server network library, and it contains built-in HTTP communication methods. So it’s possible to run a web server using just Node.js<\/strong> without any external software such as Apache. It also allows more control over how the web server works and it enables for an entire application, both client-side, and server-side, to be written in JavaScript.<\/p>\n\n\n\n

Already know the deal on Node.js<\/strong>? You might want to just jump right to how to install Node.js<\/a>.<\/p>\n\n\n\n

Asynchronous vs Thread-based Requests<\/h2>\n\n\n\n

Common server-side programs written in languages like PHP, Python, or Perl, rely on a traditional thread based model for client connections, where each connection creates an OS thread to execute the request. These typically take around 2MB of system memory at a minimum, so if you’re on a server with 1024MB of RAM, chances are when you’re approaching around 512 simultaneous client connections to the server, you could be exhausting your server’s memory.<\/p>\n\n\n\n

Node.js<\/strong> instead uses event-driven programming, so each connection uses a very small amount of memory while connecting. Then Node.js<\/strong> uses callbacks or references to inform the OS that a new connection is being requested. So the majority of the time Node.js<\/strong> does not disturb the OS, and this can lead to increased performance and efficiency.<\/p>\n\n\n\n

No or minimal file locking<\/h2>\n\n\n\n

When two or more processes share the same resource from most other server-side programs, one would have to be locked temporarily in order to allocate resources to the other process. That can cause problems where essentially processes are deadlocked and battling back and forth for the required resource, leading to delays in execution.<\/p>\n\n\n\n

Node.js<\/strong> doesn’t have this same problem as it handles almost no direct input or output operations, and so it doesn’t cause a deadlock on server resources.<\/p>\n\n\n\n

What can you do with Node.js<\/strong><\/h2>\n\n\n\n

There are a ton of different types of applications that you can build using Node.js<\/strong>, and while it is still a somewhat newer entry into the server-side programming realm, there are already a lot of options out there.<\/p>\n\n\n\n

Here are just a few examples of the types of applications that can be built using Node.js<\/strong>:<\/p>\n\n\n\n