Azure Managed Redis vs OCI Cache: engine choice and regional recovery
See how connection limits, memory-linked bandwidth, and failover responsibilities shape capacity planning for Azure Managed Redis and OCI Cache for Valkey.
Choose OCI Cache for managed Valkey in Oracle Cloud. Azure Managed Redis runs Redis Enterprise, and Azure has no first-party managed Valkey service as of September 2026. Prefer Valkey over Redis. Its broad backing across the technology industry and continued advancement of the state of the art make it the stronger direction.
Azure Managed Redis is Microsoft’s recommended replacement for Azure Cache for Redis. Azure Cache for Redis Enterprise and Enterprise Flash retire March 31, 2027. Basic, Standard, and Premium retire September 30, 2028. This comparison focuses on Azure Managed Redis. (Microsoft retirement FAQ)
At a glance
| Dimension | Azure Managed Redis | OCI Cache for Valkey |
|---|---|---|
| price (w/ 2 replicas) | no like-for-like public rate | from $30.78/GB-month |
| availability | Azure | OCI |
| engine + version | Redis 7 | Valkey 8 |
| uptime SLA | 99.999% | 99.95% |
| support SLA | from 15 minutes | from 15 minutes |
| maximum size | 2 TB | 50 TB |
| concurrent connections | up to 200,000 | 40,000 |
About Azure Managed Redis
Azure Managed Redis is Microsoft’s managed caching service based on Redis Enterprise. It runs in Azure and offers public network access or private connectivity through Private Link. Customers choose a service tier and capacity configuration for their workload.
About OCI Cache
OCI Cache is Oracle’s managed caching service in Oracle Cloud Infrastructure. It supports Valkey and Redis, with sharded and non-sharded deployments. Customers configure memory, nodes, and sharding, and applications connect through private endpoints using supported network routing.
Recent updates
September 9, 2026 - OCI added cross-region replication. A standby region is now an option for eligible non-sharded clusters, with customer promotion and rerouting.
September 2, 2026 - Momento introduced Cluster and Flex capacity for Momento Cache. Both provide dedicated, managed Valkey resources. Cluster exposes topology choices, while Flex selects topology within capacity bounds, giving teams a choice in how they configure capacity while Momento operates the cluster.
Choose who operates Valkey
OCI Cache lets you use Valkey without taking on cluster operations. Azure’s documented Valkey path on AKS leaves those operations with your team. That self-hosted deployment is outside AKS SLA and Azure support coverage.
For teams running Valkey on Kubernetes, Momento’s Valkey Operator is a proven enterprise choice with AKS support, rolling upgrades, and zone-aware placement. The Operator is self-hosted software, separate from the managed Momento Cache service.
Account for connection and bandwidth limits
Azure’s smaller SKUs cap connections at 75,000 or less. More expensive SKUs support up to 200,000, so client count can push the capacity decision beyond dataset size. Microsoft’s connection limits by SKU show how the budget changes with memory and compute.
OCI allows up to 40,000 connections per node. Its bandwidth allocation grows with provisioned memory, so a small dataset with heavy traffic can still need a larger memory allocation. Your team chooses the capacity changes on both services.
Plan how applications recover across regions
Azure’s active geo-replication keeps multiple regions writable with eventual consistency. Applications must detect regional failure and route to another endpoint.
OCI uses asynchronous active-passive regional replication. Recovery requires promoting the read-only secondary to a standalone cluster and redirecting applications. This option supports only non-sharded clusters in selected region pairs, with at least 8 GB per node. Participating clusters cannot use backups, and unreplicated writes may be lost.
Try Momento Cache
For a regional cache with a growing application fleet, evaluate Momento Cache when you want to keep client integration stable as capacity changes.
Momento Cache puts dedicated, high-performance Valkey behind a managed gateway that keeps client integration stable as your application grows. Choose Cluster for direct control over instance types, shards, and replicas, or Flex to set capacity and replication bounds while Momento selects the topology. Both include built-in autoscaling and fully managed cluster operations.
Talk to a Momento solution engineer to evaluate the capacity model and configuration that fit your workload.
Frequently asked questions
Does Azure’s five-nines SLA cover one regional endpoint?
No. Azure’s 99.999% commitment covers at least three eligible instances in three regions using active geo-replication. Group downtime requires all endpoints to be unavailable. (Azure service-level agreement)
What changes when migrating from Azure Cache for Redis?
You need new endpoints and credentials. Azure Managed Redis clusters by default, so the client changes depend on your source tier. Microsoft’s migration guidance covers the transition.
Which client mode does a sharded OCI cache need?
OCI sharded deployments require cluster-mode clients with hostname support. Applications also need suitable routing to the private endpoint. Review that integration before changing the cluster layout. (OCI connection guidance)