Single-zone instances Stay organized with collections Save and categorize content based on your preferences.
This page gives an overview of single-zone instances for Memorystore for Valkey.
For instructions on provisioning a single-zone instance seeCreate a single-zone instance.
By default, Memorystore for Valkey distributes an instance's nodes evenly amongavailable zones. For diagrams that show how nodes are distributed with thissetup, seeHigh availability and replicas.
Alternatively, you can choose to create a single-zone instance. Single-zoneinstances have lower latency than multi-zone instances because you can placeyour clients in the same zone as the Valkey nodes and avoid cross-zonecommunication.
You choose the zone distribution mode (single-zone or multi-zone) duringinstance creation. After it's created, the zone distribution mode can't bechanged.
If you connect to a single-zone instance from a client in the same zone, thenyou aren't charged forConsumer Data Processing.For more information, seeNetwork pricing.
Although we recommend provisioning a multi-zone instance withHigh Availability, you should use the following recommendations for single-zone instances if they apply to you:
If you choose to provision a single-zone instance, you should enablereplicas. Replicas reduce shard hotspots and make shards moreresilient against single-node failures.
If you choose to provision an instance without replicas, you should stilluse a single-zone instance. For more information, seeWhen to use a single-zone instance.
Single-zone instance diagram example

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-19 UTC.