Managed Redis Options Compared

ElastiCache, Azure Cache for Redis and Memorystore run Redis, and now on AWS and Google Cloud Valkey, as a service inside your account: multi-AZ replication, automatic failover, backups and patching, billed as node-hours. They are the right answer for a cache or session store that lives in the same cloud as the application. Their support tier covers the service; the memory growth, eviction storm or slow command that is actually causing your latency is usually yours to diagnose, which is why estates on managed caches still carry Redis-layer support.

Redis Ltd's managed form of Redis Enterprise: active-active geo-replication, the enterprise modules, a management layer, and vendor support for all of it. If you need those features, this is the managed way to get them. If you do not, you are paying for a product when what you need is an engineer, which is the distinction the Redis Enterprise support post works through.

You run Redis on whatever infrastructure the estate already has, on-premises, VMware, Kubernetes or a cloud VM, and a senior engineer is on the other end of the contract when something breaks and alongside you for HA design, sizing and migration. It keeps version, persistence, data model and residency entirely yours, at a cost below any managed service, and it is the only option for estates that cannot move the data or run a build the platforms do not offer. Valkey is a first-class choice here.

1. Is it a cache or session store in the same cloud as the app? If yes, that cloud's managed cache, with Redis-layer support if the workload is production-critical.
2. Do you need active-active geo-replication or the enterprise modules? If yes, Redis Cloud or self-hosted Redis Enterprise.
3. Is the estate on-premises, on VMware, or unable to move the data? If yes, self-managed with a support contract.
4. Is Valkey on the roadmap? Choose an option that covers it: ElastiCache or Memorystore's Valkey engines, or self-managed with a contract that names both builds.