Memorystore for Valkey vs Azure Managed Redis: engine choice and client growth

Choose Memorystore for Valkey for managed Valkey on Google Cloud. Azure Managed Redis runs Redis Enterprise, and Azure has no first-party managed Valkey service as of September 2026. Prefer Valkey over Redis for its broad backing across the technology industry and continued advancement of the state of the art. For an Azure workload, Momento’s managed Valkey preview and customer-operated Valkey are additional paths.

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’s retirement FAQ)

At a glance

About Google Cloud Memorystore

Google Cloud Memorystore for Valkey is a managed caching service built on Valkey. It offers cluster-enabled and cluster-disabled deployments in Google Cloud, with customers choosing node types, capacity, and topology. Memorystore for Redis and Redis Cluster are separate related offerings.

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 24, 2026 - Google made its current Valkey 9 release generally available. Its current version table lists that release as the default. For an existing Memorystore deployment, the upgrade is a one-way version decision because supported upgrades cannot be downgraded afterward.

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 the engine and who operates it

Memorystore gives Google Cloud teams managed Valkey through private connectivity, with no public endpoint. Azure Managed Redis offers managed Redis Enterprise with public access or Private Link. Cloud placement therefore determines which first-party managed engine you can use.

For Valkey on Azure, Microsoft’s AKS guide provides a customer-operated deployment. Your team operates that open-source software, which is outside AKS SLA and Azure support coverage.

Momento’s Valkey Operator is a proven enterprise choice for teams running Valkey on Kubernetes. It works with AKS and manages pod lifecycles directly, with rolling upgrades and zone-aware placement. The Operator is self-hosted software, separate from Momento Cache, so your team still operates the Kubernetes environment.

Size for the next change, including client growth

Memorystore offers six regular node types for clustered deployments, each with a predefined CPU and memory combination. Your team chooses nodes and shards and can deploy the Memorystore Cluster Autoscaler to adjust shard counts from CPU and memory metrics.

Azure’s broader catalog offers more memory and CPU combinations, but the scaling path still has limits. You cannot resize between in-memory and Flash tiers. Scaling down requires a compatible CPU and shard configuration, plus enough memory for the data.

Client growth can push Azure spending up even when memory needs stay modest. Smaller SKUs cap connections at 75,000 or less. More expensive SKUs support up to 200,000. Use Microsoft’s connection table alongside your memory forecast when choosing capacity.

Try Momento Cache

Consider Momento when client growth or recurring resize decisions are taking attention from the application. The Operator above serves the separate self-hosted Kubernetes path.

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

Can Memorystore switch cluster mode as the application grows?

Cluster mode cannot change in place. Clustered instances use sharding and cluster-aware clients. Nonclustered instances use one shard and ordinary clients. You can resize capacity within either mode, so choose the client model up front.

What do the top uptime SLAs cover?

Memorystore’s 99.99% SLA applies to qualifying multi-zone high-availability deployments. Mexico and Stockholm have a 99.95% commitment.

Azure’s 99.999% commitment requires at least three eligible high-availability, zone-redundant instances in three regions using active geo-replication. It measures the group, with downtime counted when all endpoints are unavailable.

What changes when migrating from Azure Cache for Redis?

Plan for new endpoints and credentials. Azure Managed Redis clusters by default, so client changes depend on the legacy tier you are leaving. Include that work in your migration plan alongside the retirement deadline.