Memorystore for Valkey

gcpCachegoogle-memorystore-valkey

Managed Valkey instance in single-shard or cluster mode.

Provider
gcp
Kind
Cache
Category
Data
Properties · 5 set by this component
propertytypevaluesrequiredkind defaultthis component
clusterMode · component propertyenumcluster-enabled | cluster-disabledno—inherited
evictionPolicyenumlru | lfu | ttl | noneno—inherited
hashing · advancedenumnone | consistentnonone▸ consistent
invalidationenumttl | event | nonenottlinherited
managedboolean—nofalse▸ true
materialised · advancedboolean—nofalseinherited
persistenceboolean—nofalse▸ false
readBarrier · advancedboolean—nofalseinherited
replicaCount · component propertyinteger—no0inherited
replicationenumnone | single-az | multi-az | multi-regionnonone▸ none
shardCount · component propertyinteger—no—inherited
shardsinteger—no—inherited
structure · advancedenumkey-value | bloom-filter | hash-set | sorted-setnokey-value▸ key-value
tier · advancedenumcore | edgenocoreinherited
ttlJitter · advancedboolean—nofalseinherited
ttlSecondsinteger—no—inherited
usedAsPrimaryStore · advancedboolean—nofalseinherited
Rules that apply · 3

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

cache-as-primary-store-without-persistence

This cache is the only copy of its data and has persistence turned off. A restart loses the data outright.

  • — all of these hold:
  • — the node's `usedAsPrimaryStore` is true
  • — the node's `persistence` is false
cache-missing-eviction-policy

A cache with no declared eviction policy inherits whatever the vendor chose, and most vendors default to evicting nothing. The cache fills up and then starts refusing writes.

  • — any of these hold:
  • — the node's `evictionPolicy` has no value
  • — the node's `evictionPolicy` is "none"
materialised-cache-without-rebuild-path

A cache holding materialised views has to be rebuildable from a durable store or a worker. With nothing feeding it, a cold cache is a permanent gap rather than a slow start.

  • — all of these hold:
  • — the node's `materialised` is true
  • — this does not hold:
  • — the node has at least one incoming edge from a sql-database, nosql-database, worker or stream
Use it in a design
nodes:
  - { id: "memorystore-valkey", component: "google-memorystore-valkey" }
Other Cache products · 36
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Memorystore for Valkey: managed Valkey, single-shard or cluster mode enabled. "Valkey
# product overview" states each shard has one primary and 0 to 5 replicas, distributed evenly
# across zones; the gcloud reference states --replica-count defaults to 0 replicas.
schemaVersion: "1"
type: "component"
id: "google-memorystore-valkey"
kind: "cache"
provider: "gcp"
docs: "https://cloud.google.com/memorystore/docs/valkey/product-overview"
defaults:
  replication: "none"
  persistence: false
  hashing: "consistent"
  structure: "key-value"
  managed: true
properties:
  clusterMode:
    type: "enum"
    values: ["cluster-enabled", "cluster-disabled"]
  shardCount:
    type: "integer"
  replicaCount:
    type: "integer"
    default: 0

The same page as markdown, for an agent: /catalogue/components/google-memorystore-valkey.md