Node.js Hosting from CirrusGrid PaaS

CirrusGrid PaaS provides an out-of-box integration of the fast, lightweight and highly scalable NodeJS application server. It is automatically supplied with numerous optimization and management tools to make the hosting process maximally convenient for developers.

In this article, we’ll go through the main tools and features available on the platform to provide the required level of Node.js hosting.

Node.js Environment Hosting #

To run your Node.js application, you need to set up the appropriate environment using the powerful and intuitive Topology Wizard. Switch to the Node.js tab, select the required engine version for your application server and add any other software stack required. If needed, adjust other parameters, such as cloudlets and nodes count, Public IPv4 and IPv6, etc.

nodejs tutorial

Note: Each instance is a completely isolated container, fully independent and uninfluenced by other stacks. Additionally, scaled out nodes are automatically distributed across the physical servers (or VMs) ensuring high availability.

Node.js Versioning #

Currently, the following Node.js versions are supported:

  • 6.11.5 – 6.14.1
  • 8.9.0 – 8.11.3
  • 9.0.0 – 9.11.1
  • 10.0.0 – 10.8.0nodejs cluster

You can select the required version of Node.js directly from the topology wizard during the creation of a new environment and adjust it for the existing one via container redeployment.

Node.js Application Deployment #

CirrusGrid PaaS automates the deployment process for the managed NodeJS application servers using:

  • application archive uploaded from the local machine or via external URL
  • remote VCS repository (e.g. GitHub)nodejs hosting

Tip: Usually, due to the CirrusGrid ports auto-redirect algorithm, the deployed projects are instantly accessible without any additional manipulations. Herewith, for greater accuracy, you can manually exclude some of the services from the auto-redirect search by listing the appropriate ports via the REDIRECT_EXCLUDE_PORTS variable.

You can read the appropriate documents to learn more about the deployment of the Node.js applications:

Node.js Package Managers #

For greater convenience, each NodeJS application server contains a built-in development tool called Package Manager, which provide standardization and automation of the installation, update, configuration, and removal processes.

CirrusGrid supports two types of package managers:

  • npm – manages your project requirements by installing the additional modules, packages, and ready-to-use applications
  • yarn – operates the same requirements as in npm (so no changes are required for the existing applications), while providing higher speed, reliability, and convenience

By default, the npm package manager is used for the NodeJS application servers, but, if necessary, it can be easily switched to yarn. For that, access the container variables frame and set the appropriate PACKAGE_MANAGER value (either npm or yarn).

cluster nodejs

Node.js Process Managers #

Process Managers provide the ability to control application lifecycle, monitor running services and maintain the project operability. Jelastic PaaS provides support of the following process managers for the NodeJS stack:

  • npm – initiates and configures multiple processes
  • pm2 – provides a huge variety of application management features, including the launched Node.js processes monitoring
  • forever – allows running your Node.js processes continuously and automatically restarting them upon failure
  • supervisor – monitors running applications for changes and automatically restarts required ones to keep them up-to-date

Users can choose the necessary process manager during container redeployment or by adjusting the PROCESS_MANAGER variable (using forevernpmpm2 or supervisor as value, container restart is needed to apply new options).

Domains Management #

Your Node.js application can be easily supplemented with the custom domain name to be used instead of the default one. There are two options based on your environment topology:

  • CNAME redirect if using Shared Load Balancer; is recommended for dev and test environments
  • DNS A Record if using Public IP; can handle high traffic load and is suitable for production environments

Also, you can quickly switch traffic between your environments (e.g. to redirect customers to the newer application version without downtime) by utilizing the swap domains functionality or with the help of the SwapExtIps API/CLI method.

nodejs docs

Automatic Vertical Scaling #

CirrusGrid PaaS dynamically provide the exact amount of resources (RAM and CPU) required by your nodes according to the current load with no manual intervention required. As a result, you never overpay for unused resources and save your time as the platform eliminates the need to handle the load-related adjustments or architectural changes.

You just need to set the upper cloudlets limit (each one equals to 128 MiB of RAM and 400 MHz of CPU) for your NodeJS application server and everything else will be handled by platform automatically.

ruby automatic vertical scaling

Refer to the automatic vertical scaling documentation for additional information.

Manual Horizontal Scaling #

To scale out/in NodeJS application servers, you need to access the topology wizard and click the +/- buttons within the Horizontal Scaling section to set the required number of nodes. Also,  starting with the 5.5 platform version, you can adjust the preferred scaling mode:

  • Stateless – simultaneously creates all new nodes from the base image template
  • Stateful – sequentially copies file system of the master container into the new nodesnodejs host

The maximum number of the same-type servers within a single environment layer depends on a particular hosting provider settings (usually this limit stands for 16 nodes and can be enlarged by sending the appropriate request to support).

Also, for the proper requests distribution, a load balancer instance is automatically added upon NodeJS server scaling. Refer to the horizontal scaling documentation for more details.

Automatic Horizontal Scaling #

Access the environment Settings > Monitoring > Auto Horizontal Scaling section to set up special tunable triggers, which allow to increase or decrease the number of nodes due to the application load. Configure type of resource to be monitored (CPURAMNetworkDisk) and the exact condition of scaling.nodejs env

Learn more about automatic horizontal scaling in the linked document.

In addition, hosting at CirrusGrid PaaS allows using other built-in tools and features, for example:

Get your free trial account and start exploring Ruby hosting benefits within CirrusGrid multi-cloud platform for your own applications!

Powered by BetterDocs