ElastiCache vs Azure Managed Redis: choose the managed engine first

Choose ElastiCache for managed Valkey on AWS. Azure Managed Redis runs Redis Enterprise, and Azure has no first-party managed Valkey service as of September 2026. If you need a Microsoft-managed cache on Azure, that engine tradeoff comes with the service. Then weigh ElastiCache’s automatic scaling options against Azure’s customer-selected resizing and connection limits.

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

About Amazon ElastiCache

Amazon ElastiCache is an AWS-managed caching service with Serverless and node-based deployment options. ElastiCache for Valkey runs the Valkey engine, while Redis OSS is a related offering. AWS manages infrastructure maintenance. Customers choose the deployment model and, for node-based clusters, the capacity and topology.

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.

Recent updates

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.

June 23, 2026 - AWS announced Valkey 9 support for node-based ElastiCache. New node-based deployments can select that major, while Azure Managed Redis offers Redis 7. Keep the AWS version selection separate from Serverless when evaluating deployment and client requirements.

Prefer Valkey, then choose who operates it

Prefer Valkey over Redis. It is widely backed across the technology industry and continues to advance the state of the art. ElastiCache lets you make that choice with AWS handling infrastructure replacement and patching through its managed deployment options.

Microsoft’s Valkey deployment on AKS provides a customer-operated path. Your team operates that software, which falls outside the AKS SLA and Azure support coverage.

For teams running Valkey on Kubernetes, Momento’s Valkey Operator is a proven enterprise choice. It supports AKS and manages pod lifecycles directly, with rolling upgrades and zone-aware placement. The Operator is self-hosted software, separate from the managed Momento Cache service.

Plan for traffic growth and connected clients

ElastiCache Serverless scales automatically. For anticipated demand that exceeds its scaling pace, AWS recommends pre-scaling at least 60 minutes ahead. Node-based ElastiCache also offers autoscaling options.

Azure customers monitor demand and choose resizing operations from a broad tier and size catalog. Scaling stays within tier and configuration boundaries, so the next size you need must fit the deployment you chose.

Connections can drive that sizing decision even when the dataset still fits. Azure’s smaller SKUs cap connections at 75,000 or less. More expensive SKUs support up to 200,000. Use Microsoft’s client connection limits to size for your application fleet as well as its data.

Try Momento Cache

For a growing client fleet that needs managed Valkey, consider Momento’s gateway and standalone integration. The Operator described above serves teams retaining their own Kubernetes environment.

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

How do the uptime commitments compare?

ElastiCache’s 99.99% SLA covers Serverless. Node-based Valkey qualifies with automatic failover and placement of the primary and replicas across at least two availability zones per shard.

Azure’s 99.999% commitment requires at least three eligible HA, zone-redundant instances in three regions connected through active geo-replication. It measures group availability, with downtime counted when all group endpoints are unavailable. A single region has a 99.99% commitment with zone-redundant HA. Applications still need to detect regional failure and route to another endpoint.

What changes when migrating from Azure Cache for Redis?

Azure Managed Redis requires new endpoints and credentials. It clusters by default, so the client changes depend on your source tier. Include those changes in the migration plan alongside the retirement dates above.

Which service offers a public endpoint?

Azure Managed Redis supports public access and Private Link. ElastiCache clusters have no public IP, although applications outside AWS can connect through supported networking, including production VPN access. ElastiCache Serverless also requires cluster-capable clients and TLS.