Zeema
New design
Catalogue / cache

Cache cluster

Cachecache-cluster

In-memory cache tier drawn without naming a product.

Provider
default
Kind
Cache
Category
Data
Official docs
not recorded
Properties · 1 set by this component
propertytypevaluesrequiredkind defaultthis component
evictionPolicyenumlru | lfu | ttl | noneno—inherited
hashing · advancedenumnone | consistentnononeinherited
invalidationenumttl | event | nonenottlinherited
managedboolean—nofalse▸ false
materialised · advancedboolean—nofalseinherited
persistenceboolean—nofalseinherited
readBarrier · advancedboolean—nofalseinherited
replicationenumnone | single-az | multi-az | multi-regionnononeinherited
shardsinteger—no—inherited
structure · advancedenumkey-value | bloom-filter | hash-set | sorted-setnokey-valueinherited
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 used as primary store without persistenceerror
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 without eviction policywarning
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 a rebuild patherror
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: "cache-cluster", component: "cache-cluster" }
Other Cache products · 36
ApsaraDB for Memcachealibaba-apsaradb-memcachealibabacloudcacheApsaraDB for Redisalibaba-apsaradb-redisalibabacloudcacheAmazon DynamoDB Accelerator (DAX)aws-daxawscacheAmazon ElastiCacheaws-elasticacheawscacheAmazon MemoryDBaws-memorydbawscacheAzure Cache for Redisazure-cache-for-redisazurecacheAzure Managed Redisazure-managed-redisazurecacheGeneric cachecachecachecogneecogneecacheDragonflydragonflycacheEVCacheevcachecacheMicrosoft GarnetgarnetcacheVMware GemFiregemfirecacheGraphitigraphiticacheHazelcasthazelcastcacheApache IgniteignitecacheInfinispaninfinispancacheKeyDBkeydbcacheLettalettacacheMem0mem0cacheMemcachedmemcachedcacheRedisrediscacheRedis Cloudredis-cloudcacheSquidsquidcacheTrickstertrickstercacheUpstash RedisupstashcacheValkeyvalkeycacheVarnish CachevarnishcacheZepzepcacheMemorystore for Redisgoogle-memorystoregcpcacheMemorystore for Memcachedgoogle-memorystore-memcachedgcpcacheMemorystore for Redis Clustergoogle-memorystore-redis-clustergcpcacheMemorystore for Valkeygoogle-memorystore-valkeygcpcacheIBM Cloud Databases for Redisibm-databases-for-redisibmcacheOCI Cache with Redisoci-cache-redisocicacheOCI Cache with Valkeyoci-cache-valkeyocicache
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Generic in-memory cache tier whose product the design does not name. No eviction policy,
# no persistence and no replication are assumed; the lint rules ask for them.
schemaVersion: "1"
type: "component"
id: "cache-cluster"
kind: "cache"
provider: "default"
defaults:
  managed: false

The same page as markdown, for an agent: /catalogue/components/cache-cluster.md