New at Compose: Horizontal Scaling for Redis and more scaling control

Published

If you are a Compose user, then from today, you will find a new Resources console ready for you to take more control of your database scaling. And if you use Redis on Compose you'll find that new console has enabled support for Read-only slaves. It's all about scaling today at Compose - just like every day.

People love how Compose looks after their scaling needs. There's no running out of capacity with Compose databases; when you need more space or RAM, autoscaling kicks in and scales your database up without interruption. It's simple and effective and it makes running your databases at Compose a breeze. If you wanted to you could reach for the Scaling slider and bump up your resources before you needed them too, preempting a large import or traffic from a launch. Even simpler.

We listen too. We heard you wanted more control of your deployments scaling. That's why we've just launched a new element to the Compose console, Resources. Each database deployment now has a Resources sidebar menu which gives you a detailed view of how your database is using resources and more controls to let you scale up those resources. Here's what it looks like:

Now you can see memory and storage allocated to database nodes and you can scale up your TCP, SSH, and other portals; you've been able to horizontally scale them in the Security view for some time. Each Resources view is customized to the database type underneath and that now enables us to offer new scaling options. First to benefit from that is Redis, as you may be able to tell from the screenshot above.

Redis Read-only Slaves

Redis Read-only Slaves can be added to your Redis deployments now for those situations where you want to give large numbers of clients the ability to view your fast moving Redis data. Read-only slaves can also provide a great place to execute long-running queries which could block your Redis master for a performance-killing amount of time.

Each read-only slave is synchronized to the master Redis server and has its own TCP portal, so incoming request traffic doesn't impact on the rest of the Redis deployment. As you add slaves to your Redis deployment, the overview will expand to list new connection strings and command lines to connect to each of them.

You can have up to ten read-only slaves, each one provisioned with the same amount of memory as the master and secondary Redis nodes and priced accordingly. The best part is it is, as always with Compose, simple:

Drag the slider, click Confirm and you have read-only slaves on your Redis.

Visible pricing

Talking about prices, the new Resources views will always give you the cost of any scaling you make and can show you the price of the changes you are making and how it will affect the total cost of your deployment. You can see that above in the read-only slave slider screenshot. You can see how much you are paying currently for the feature, what the difference in pricing will be, the new total for the feature and the total cost for the deployment. Please, remember these are the estimated monthly costs; billing is calculated on a pro rata hourly basis, so you can scale up and down when it suits you.

To learn more about resources and scaling, check out the Resources and Scaling documentation online which includes links to pages about each databases' scaling capabilities.


If you have any feedback about this or any other Compose article, drop the Compose Articles team a line at articles@compose.com. We're happy to hear from you.

Image by Evan Kirby
Dj Walker-Morgan
Dj Walker-Morgan is Compose's resident Content Curator, and has been both a developer and writer since Apples came in II flavors and Commodores had Pets. Love this article? Head over to Dj Walker-Morgan’s author page and keep reading.