Compose Database-as-a-Service Help and Documentation

Everything you need to know about Compose, Hosted or Enterprise, is here in our help system. Whether you run one database for your businesses' sole application or six different databases to support an entire corporation, we've got the information you need.

Resources and Scaling

The Resources view allows you to control the resources which are allocated to your deployments. These resources include increasing RAM and storage (vertical scaling) or adding database nodes (horizontal scaling).

Vertical and Horizontal Scaling of Databases

Vertical scaling within a database deployment involves adding storage and memory resources to each database instance within the deployment. It is the most immediate way to increase performance for most databases. It does not require any code or configuration changes of the applications using the deployment. Compose has always offered vertical scaling options, including but not limited to, autoscaling databases.

Horizontal scaling within a database deployment involves adding more database nodes to handle the data. Typically, they are created with resources matching the other nodes so they can be scaled vertically alongside the existing nodes too. Horizontal scaling may dependent on the underlying database, require some changes to application or database configuration to make effective use of the additional nodes.

Scaling database types

Database
Database scaling modes

Vertical, Horizontal for Enterprise

Vertical

Vertical, Horizontal

Vertical, Horizontal for Enterprise

Vertical

Vertical

Vertical

Vertical, Horizontal for Enterprise

Vertical, Horizontal

Vertical and horizontal scaling portals

Access to the databases within a database deployment is managed by portals. These are small nodes dedicated to managing traffic between the outside internet and the database nodes inside the private network where the database deployment resides. Compose has offered the ability the add more portals, that is to horizontally scale portals, for some time where the database can benefit from more access capability. There are times when these portals need more resources to handle more traffic. This vertical scaling is possible with through Resource sidebar menu for deployments.

The Resources view

When the Resources view is selected, the system will show information about the current nodes.

A view of a deployment's resources, specifically Elasticsearch.

A view of a deployment's resources, specifically Elasticsearch.

The view will vary from database type to database type. For this Elasticsearch database, we see three panels.

The Nodes panel

This displays information about the database nodes. Each row represents one database node in the deployment. The rows may be grouped into types of database node with some databases.

At the top right of the panel is information about how the nodes are currently scaled. Each row shows each capsule's name, region and IP address (on the VLAN).

To vertically scale across the nodes, click the Scale button in the lower-right of the panel. This will take you to a screen where you can adjust resources allocated to each node's capsule.

A view of the scale slider, specifically the slider for Elasticsearch.

A view of the scale slider, specifically the slider for Elasticsearch.

Portal panels

There may be one or more Portal panels, depending on what portals types a database deployment supports. TCP and SSH portals are available for many deployments while others have database specific portals such as MongoDB and RethinkDB.


Still Need Help?

If this article didn't solve things, summon a human and get some help

Resources and Scaling