Node.js is an avant-garde event-driven system, which is used to create scalable applications. It is built with the Google V8 JavaScript engine and it handles requests and responses between a server and a large number of users much more effectively than any conventional platform. What makes Node.js one of a kind is the fact that in contrast to traditional platforms which process the information in giant chunks, it processes everything in tiny bits. For instance, in case a user has to fill a couple of fields on an Internet site, Node.js processes the info in the first field the second it is typed, utilizing the server processing time more efficiently. In contrast, other platforms wait for all the fields to be filled out and while the information in them is being processed, requests from other users stay in the queue. The difference may be insignificant for a single person, but it absolutely does make a difference if an enormous number of people are visiting a site at the same time. A couple of examples of sites where Node.js can be used are online dinner reservation portals, online chat rooms or interactive browser-based video game portals, in other words sites that need fast real-time interaction.

Node.js in Hosting

If you host a web app on our advanced cloud platform and you would like to try Node.js, you’ll be able to add it to your web hosting account regardless of the hosting plan that you use. You can make this via the Upgrades section in the Hepsia Control Panel and you’ll be able to take advantage of Node.js in no more than several minutes after you add this service to the account. You’ll be able to select how many instances you want to add to the account – one instance means one application using Node.js. In the new section that will appear in the Control Panel, you can specify the path to the .js file in your web hosting account and select if that file will be accessible via the shared IP of the physical server or via a dedicated IP. Our system will also specify a port number for the connection. You’ll be able to disable or to reboot each instance independently, in case it is necessary.