Azure Managed Redis

azureCacheazure-managed-redis

Managed Redis Enterprise with high availability and active geo-replication.

Provider
azure
Kind
Cache
Category
Data
Properties · 3 set by this component
propertytypevaluesrequiredkind defaultthis component
activeGeoReplication · component propertyboolean—nofalseinherited
evictionPolicyenumlru | lfu | ttl | noneno—inherited
hashing · advancedenumnone | consistentnononeinherited
highAvailability · component propertyboolean—notrueinherited
invalidationenumttl | event | nonenottlinherited
managedboolean—nofalse▸ true
materialised · advancedboolean—nofalseinherited
persistenceboolean—nofalse▸ false
readBarrier · advancedboolean—nofalseinherited
replicationenumnone | single-az | multi-az | multi-regionnonone▸ multi-az
shardsinteger—no—inherited
sku · component propertyenummemory-optimized | balanced | compute-optimized | flash-optimizedno—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-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: "managed-redis", component: "azure-managed-redis" }
Other Cache products · 36
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Azure Managed Redis: managed Redis Enterprise, the successor to Azure Cache for Redis.
# "What is Azure Managed Redis?": high availability is on by default with primary and replica shards
# on at least two nodes, and in regions with availability zones nodes are spread across zones by
# default; data persistence and active geo-replication are opt-in features.
schemaVersion: "1"
type: "component"
id: "azure-managed-redis"
kind: "cache"
provider: "azure"
docs: "https://learn.microsoft.com/en-us/azure/redis/overview"
defaults:
  managed: true
  persistence: false
  replication: "multi-az"
properties:
  sku:
    type: "enum"
    values: ["memory-optimized", "balanced", "compute-optimized", "flash-optimized"]
  highAvailability:
    type: "boolean"
    default: true
  activeGeoReplication:
    type: "boolean"
    default: false

The same page as markdown, for an agent: /catalogue/components/azure-managed-redis.md