Azure Managed Redis vs Dragonfly Cloud: engine control and client growth
Compare engine control, connection limits, replicated RAM pricing, and uptime commitments before choosing a managed cache and its growth path.
Azure has no first-party managed Valkey service as of September 2026. Azure Managed Redis runs Redis Enterprise, with customer-selected resizing and connection limits tied to the SKU. Dragonfly Cloud runs its own company-controlled engine, with horizontal scaling through Swarm. The choice turns on which engine dependency and capacity constraints your team is prepared to adopt.
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 | Dragonfly Cloud |
|---|---|---|
| price (w/ 2 replicas) | no like-for-like public rate | from $24.00/GB-month |
| availability | Azure | AWS, Google Cloud, Azure |
| engine + version | Redis 7 | proprietary |
| uptime SLA | 99.999% | 99.95% |
| support SLA | from 15 minutes | from 1 hour |
| maximum size | 2 TB | 15 TB |
| supported clients | RESP-compatible (cluster or standalone) | RESP-compatible (cluster or standalone) |
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 Dragonfly Cloud
Dragonfly Cloud is a managed service built on the Dragonfly engine. Dragonfly is a separate implementation with a Redis-compatible API. The service offers standalone datastores and sharded Swarm deployments, with client requirements that depend on the selected mode.
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.
Choose who controls the engine’s future
Dragonfly is a separate project maintained by one company, which controls license terms for future releases. That dependency matters when choosing an engine for a long-lived application. Redis’s 2024 licensing change provides a historical example, discussed in Momento’s account of the Redis licensing change.
For Valkey on Azure, Microsoft documents a customer-operated deployment on Azure Kubernetes Service (AKS). User-deployed open-source software is outside the AKS SLA and Azure support coverage. Momento’s Valkey Operator is a proven enterprise choice for this Kubernetes path, with rolling upgrades and zone-aware placement. It is self-hosted software, separate from managed Momento Cache.
Plan around connection and scaling constraints
Azure offers a broad tier and size catalog, but your team monitors demand and initiates resizing. Scaling cannot cross between in-memory and Flash tiers. Connection limits can also push you toward a higher bill. Smaller SKUs cap connections at 75,000 or less, while more expensive SKUs support up to 200,000.
Dragonfly Swarm provides managed horizontal scaling beyond one server. Swarm requires cluster-aware clients, and cluster mode cannot change on an existing datastore. Memory and compute can resize, and the Business plan lists autoscaling.
Try Momento Cache
If you want Valkey’s broad industry backing and stable client integration through a sharding transition, evaluate Momento.
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
What do the top uptime SLAs cover?
Azure’s 99.999% SLA covers a qualifying group of at least three HA, zone-redundant instances in three regions using active geo-replication. Group downtime requires all endpoints to be unavailable. Dragonfly’s 99.95% commitment averages shard availability. (Azure SLA, Dragonfly SLA)
What changes when migrating from Azure Cache for Redis?
Azure Managed Redis uses new endpoints and credentials, and it clusters by default. The client changes needed depend on your source tier. (Microsoft retirement FAQ)
Does Dragonfly’s burst bandwidth describe sustained capacity?
No. Its AWS Standard 12.5 GB example lists 0.5 Gbps baseline and 10 Gbps temporary, non-guaranteed burst. Bandwidth varies by cloud, memory, and compute tier. (Dragonfly bandwidth guide)
Can Dragonfly scale capacity automatically?
Dragonfly offers autoscaling in its business tier. Swarm still requires cluster-aware clients, so choose the client mode before creating the datastore. (Dragonfly plans)