Database Horizontal Scaling

With Jelastic you are able to scale both SQL and NoSQL databases:

database scaling

Each newly added database server has its own host name (which consists of DB name, node ID and environment’s host) and credentials for administrator access, that you’ll receive in separate email notifications after addition.

The scaling out approach for database servers implies a completely new node addition, i.e. created servers will have the default content (the existing databases and records of the initial DB server won’t be copied to the new instances). In such a way, after increasing the number of database nodes, you’ll receive a set of independent servers.

Tip: You are also able to automate database horizontal scaling based on incoming load with the help of tunable triggers.

You can also reset the password not just for a separate DB server, but for the whole set of databases in case it’s necessary to regain administrator access for all of them:

database reset password

For ensuring your data security and gaining the increased performance, it makes sense to configure the replication between the servers of your DB cluster. Jelastic provides you with two flows to setup a DB cluster:

Auto-Replication

With Jelastic, you can get the database clustering solution automatically adjusted just in a few clicks using the appropriate one-click installation widgets below. Just click Get it hosted now, type your email and choose the preferable Jelastic installation.

Tip: In case you don’t have an account, you can use Jelastic Cloud Union for the better comparison of our partners.

master slave replication

MySQL master-slave replication:


MariaDB master-slave replication:


PostgreSQL master-slave replication:


MongoDB master-slave replication:


As a result, you’ll get a separate environment with the complete DB cluster of 2 servers and the already configured master-slave replication between them just in a minute, skipping all the steps of manual configuration. With such a solution, you enable data from one database node (master) to be replicated to another server (slave), which can be used to solve performance problems, to support the DB backups and to alleviate system failures.

These widgets can be also found at our Marketplace site page or at the corresponding Marketplace section in your dashboard.

Manual Replication

Sometimes, it may be preferable for your DB cluster to include more than just two servers or you may want to set up replication for the already existing environment with your application deployed. In such a case, please, follow one of the instructions below (depending on the chosen database system):

We are also going to automate these operations in the nearest future in order to make our platform even more easy-to-use and to save your time for coding.