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.

Redis on Compose

About Compose Redis Deployments

Compose Redis Deployments allow developers to focus on what they do best (developing useful applications) and avoid the guesswork of capacity planning. These deployments are configured with fast SSDs, are fully replicated, and have access to huge amounts of RAM. As an application’s data size increases, the deployment resources can scale fluidly to maintain consistent performance, and are billed based on actual usage.

Redis requires fast IO and as much RAM as the total data size. Increasing deployment server capacity traditionally requires a change in server size, replacement of IO subsystems, and a coordinated operations process. Developers typically perform a precarious balancing act, trying to avoid unnecessary cost, while hoping that their data growth won’t take them by surprise and lead to poor performance, or even worse, deployment outages.

In addition to autoscaling, Redis Deployments include built-in daily backups so you can be confident that your data will never be lost. Backups use the Redis dump command to perform the backup to ensure minimal impact to your applications.


  • Automatically scaling server stack that scales RAM, CPU, and I/O as your Redis data grows.
  • Easy to select Cache-mode and Maxmemory policy
  • Slow log control and viewer
  • 2 node clusters on extremely fast SSDs (solid state drives).
  • Guaranteed resources per deployment.
  • No-cost backups, no matter how big your deployment grows.
  • Start with 256MB for $20.50 - as you grow each additional 256MB costs $13.

Data Center Availability

See Compose Datacenter Availability for current location availability.

High Availability

All Redis Deployments are high-availability clusters. You get fully redundant architecture from the hardware to your deployment itself. Redis clusters consist of a master and slave member as well as Sentinels to handle node failures. In the event of a master member failure, we've configured Sentinel to promote the current slave so your applications should experience little to no impact.

Each Redis deployment comes with a proxy to provide a single member connect string so there's no worrying with which member is currently master.

Storage/Cache Mode

Redis can run as a cache, setting fixed limits on memory and then managing it according to a preset policy. We expose these features in the Compose web console making it simple to enable and disable Cache mode or set the policy, from the default "volatile-lru" to "noeviction", "allkeys-lru", "allkeys-random", "volatile-random" or "volatile-ttl" depending on your needs.

To make things simpler though, we have two basic modes, Storage and Cache, which can be selected in the console and this will set memory management rules for Redis. Read more in Redis Cache and Storage Modes.


Compose Redis has the ability to import data from other Redis systems available over the internet. Read more on the help page - Redis Import.

Slow Logs

Redis's Slow Logs allow you to get insight into what operations are taking longer than a selected time. With Compose, you don't have to go to the command line to get that insight as it's visible from the Compose console. Read more about it in Redis Slow Logs .


Compose Redis exposes a number of commonly used configuration settings in a simple interface. Read more about it in Redis Configuration.

Still Need Help?

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

Redis on Compose