Amazon DynamoDB Accelerator (DAX)

Write-through in-memory cache in front of DynamoDB with a five minute item cache TTL.

Provider: aws
Kind: Cache
Category: Data
Official docs: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.concepts.html

Properties · 7 set by this component

property	type	values	required	kind default	this component
encryptionAtRest · component property	boolean	—	no	false	inherited
evictionPolicy	enum	lru \| lfu \| ttl \| none	no	—	▸ lru
hashing · advanced	enum	none \| consistent	no	none	inherited
invalidation	enum	ttl \| event \| none	no	ttl	▸ ttl
managed	boolean	—	no	false	▸ true
materialised · advanced	boolean	—	no	false	inherited
persistence	boolean	—	no	false	inherited
queryCacheTtlSeconds · component property	integer	—	no	—	inherited
readBarrier · advanced	boolean	—	no	false	inherited
replication	enum	none \| single-az \| multi-az \| multi-region	no	none	inherited
shards	integer	—	no	—	inherited
structure · advanced	enum	key-value \| bloom-filter \| hash-set \| sorted-set	no	key-value	▸ key-value
tier · advanced	enum	core \| edge	no	core	▸ core
ttlJitter · advanced	boolean	—	no	false	inherited
ttlSeconds	integer	—	no	—	▸ 300
usedAsPrimaryStore · advanced	boolean	—	no	false	▸ false
writeThrough · component property	boolean	—	no	true	inherited

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: "dax", component: "aws-dax" }

Other Cache products · 36

ApsaraDB for Memcachealibaba-apsaradb-memcachealibabacloudcache ApsaraDB for Redisalibaba-apsaradb-redisalibabacloudcache Amazon ElastiCacheaws-elasticacheawscache Amazon MemoryDBaws-memorydbawscache Azure Cache for Redisazure-cache-for-redisazurecache Azure Managed Redisazure-managed-redisazurecache Generic cachecachecache Cache clustercache-clustercache cogneecogneecache Dragonflydragonflycache EVCacheevcachecache Microsoft Garnetgarnetcache VMware GemFiregemfirecache Graphitigraphiticache Hazelcasthazelcastcache Apache Igniteignitecache Infinispaninfinispancache KeyDBkeydbcache Lettalettacache Mem0mem0cache Memcachedmemcachedcache Redisrediscache Redis Cloudredis-cloudcache Squidsquidcache Trickstertrickstercache Upstash Redisupstashcache Valkeyvalkeycache Varnish Cachevarnishcache Zepzepcache Memorystore for Redisgoogle-memorystoregcpcache Memorystore for Memcachedgoogle-memorystore-memcachedgcpcache Memorystore for Redis Clustergoogle-memorystore-redis-clustergcpcache Memorystore for Valkeygoogle-memorystore-valkeygcpcache IBM Cloud Databases for Redisibm-databases-for-redisibmcache OCI Cache with Redisoci-cache-redisocicache OCI Cache with Valkeyoci-cache-valkeyocicache

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# DynamoDB Accelerator (DAX): write-through in-memory cache in front of DynamoDB tables.
3# "DAX: How it works" gives the item cache a Time to Live of 5 minutes by default, an always-on LRU
4# eviction list, and states that DAX serves eventually consistent reads only; encryption at rest and
5# in transit are chosen when the cluster is created ("In-memory acceleration with DAX").
6schemaVersion: "1"
7type: "component"
8id: "aws-dax"
9kind: "cache"
10provider: "aws"
11docs: "https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAX.concepts.html"
12defaults:
13  managed: true
14  evictionPolicy: "lru"
15  ttlSeconds: 300
16  invalidation: "ttl"
17  structure: "key-value"
18  tier: "core"
19  usedAsPrimaryStore: false
20properties:
21  queryCacheTtlSeconds:
22    type: "integer"
23  writeThrough:
24    type: "boolean"
25    default: true
26  encryptionAtRest:
27    type: "boolean"
28    default: false

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