Automatic Vertical Scaling

Objective

This guide explains how to use Automatic Vertical Scaling on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.

Before you begin

• Sign in with an account permitted to manage the relevant environment.
• Confirm the target environment, region and resources before saving changes.
• Create a backup or rollback plan before changing a production system.

Ruk-Com Cloud is the only PaaS that can automatically scale applications vertically andHorizontalThis makes hosting your application more flexible.

Automatic vertical scalingAutomatic vertical scaling by dynamically changing the amount allocated to server resources (RAM and CPU) based on current demand without manual intervention. We guarantee that with this feature you will not overpay for unused resources and save your time. This eliminates the need to manage load-related modifications or architectural changes.

Simply set the maximum limit you have available and the platform will automatically determine the amount of resources required for your app and can track incoming load in real time.

How does scaling work?

The main idea of auto-scaling is quite simple - as soon as the load of an application increases, the platform increases the resources available to it, and when the load decreases again, the resources automatically decrease with the platform.

Resources are allocated immediately without any delay or impact on your application, as can be learned from the next video:

Tips:The vertical scaling feature is available for all instance types in the environment (such as application server, database, load balancer, Docker container, Elastic VPS, cache instances, and build nodes).

As you can see in the video above, Jelastic measures resources in special units called cloudlets, which have superior scaling details equivalent to approximately 128 MiB RAM and 400Mhz CPU cores.

There are two types of Cloudlets:reservedanddynamic

• ReservedReserved resource cloudlets are used to determine exactly how many resources are expected to be used in your application, and you pay for those resources regardless of actual usage. However, when compared the price is dynamically lower.
  
  
• DynamicCloudlets determine how many resources your application can access as needed, paying only for actual use.

Automatic vertical scalingAutomatic vertical scalingIt operates within the limits of the specified number of dynamic cloudlets. You can limit scalability with appropriate settings, and this way you can effectively budget where you want and prevent unexpected cost spikes.

You can combine the two types of cloudlets in several ways by following the pricing model that works best for you.

Adjusting resource limits

A newly created environment receives a number of cloudlets. Resource usage depends on the type and amount of software stack. When added to the environment, each stack receives a default value like this:

The number of cloudlets allocated is based on the optimal amount of resources required for proper functioning.

If you want to change these values and scale your environment based on the maximum number of available resources (cloudlets), you can manually increase/decrease them viaEnvironment topologywizard using the cloudlet slider in the Vertical Scaling section.

More:If the scaling limit (i.e., the number of dynamic cloudlets) is changed for an existing application server, database, or cache node, the relevant layer will be restarted with an appropriate warning displayed in the topology wizard.

You can use automatically collected statistics to check last month's usage levels and set resource amounts accordingly. And in case your application is very popular and the capacity of a single server is not enough. You can scale horizontally by increasing the number of nodes manually or by setting a set.Trigger for automatic horizontal resizingof your application server