[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-19。"],[],[],null,["# Memorystore for Valkey overview\n\nMemorystore for Valkey is a fully managed Valkey service for Google Cloud which supports both Cluster Mode Enabled and Cluster Mode Disabled instances. Applications\nrunning on Google Cloud can achieve extreme performance by leveraging the highly\nscalable, available, secure Valkey service without the burden of managing complex\nValkey deployments.\n\nKey concepts and terms\n----------------------\n\n### Cluster Mode Enabled and Cluster Mode Disabled instances\n\nMemorystore for Valkey instance can be created in both Cluster Mode Enabled and Cluster Mode Disabled modes. While a Cluster Mode Enabled instance can have one or more shards, a Cluster Mode Disabled instance runs on a single shard. For more details see [Enable and disable Cluster Mode](/memorystore/docs/valkey/cluster-mode-enabled-and-disabled).\n\n### Hierarchical resource structure\n\nMemorystore for Valkey gathers the various resources used in a Valkey deployment\ninto a hierarchical structure that simplifies administration and management.\nHere is a diagram that illustrates this structure:\n\nMemorystore for Valkey instances are composed of a set of shards, each\ncontaining a subset of your key space. Each shard in an instance\nis composed of one primary node, and optionally up to two replica nodes.\nWhen replica nodes are added, Memorystore automatically\ndistributes the nodes of a shard across zones to provide higher availability and\nthroughput.\n\n### Instances\n\nWhen provisioning a Memorystore for Valkey instance, you must provision enough\nshards to serve the keyspace of your entire application. For details about\ninstance specification, see [Instance and node specification](/memorystore/docs/valkey/instance-node-specification).\n\n### Shards\n\nYour instance is composed of multiple equally sized shards. For details about shard specification, see [Instance and node specification](/memorystore/docs/valkey/instance-node-specification).\n\n### Primary and replica nodes\n\nThere is one primary node per shard. Each shard can have 0, 1, or 2 replica\nnodes. Replicas provide high availability and additional read throughput, and\nare evenly distributed across zones.\n\nFor more details see [High availability and replicas](/memorystore/docs/valkey/ha-and-replicas).\n\n### Valkey version\n\nMemorystore for Valkey supports Valkey versions 7.2 and 8.0. For more information about the features introduced by each version, see [Supported versions](/memorystore/docs/valkey/supported-versions). Memorystore for Valkey supports a [subset of the\ntotal Valkey command library](/memorystore/docs/valkey/supported-commands).\n\nInstance endpoints\n------------------\n\n- **Cluster Mode Enabled:** Each instance has a discovery endpoint to which your client connects. Your client also uses the discovery endpoint for node discovery. For more\n information, see [Instance endpoints for Cluster Mode Enabled](/memorystore/docs/valkey/instance-node-specification#cluster_instance).\n\n- **Cluster Mode Disabled:** Each instance has a primary endpoint and a reader endpoint. The primary endpoint always directs traffic to the primary node, while the reader endpoint load-balances read queries across available replicas automatically. For more information, see [Instance endpoints for Cluster Mode Disabled](/memorystore/docs/valkey/instance-node-specification#cluster_mode_disabled_instance).\n\nNetworking prerequisites\n------------------------\n\nBefore you can create a Memorystore for Valkey instance, you must set up\n[Networking](/memorystore/docs/valkey/networking) for your project.\n\nBilling\n-------\n\nSee the [Pricing](/memorystore/docs/valkey/pricing) page for information on\npricing for available regions."]]
