Vintner
Plant a Vine

Caches

Redis and Valkey cache instances — node types, clustering, and multi-AZ.

Caches

The caches section configures managed in-memory cache instances. Multiple caches can be added per vine.

Fields Per Cache

FieldTypeDescription
NameText inputUnique per vine, lowercase
EngineSelectredis or valkey
Node TypeSelectInstance size with pricing shown
NodesNumber1–6 cache nodes
Multi-AZToggleEnable automatic failover across availability zones

Engines

EngineDescription
RedisThe standard in-memory data store. Supported on all three providers.
ValkeyOpen-source Redis fork (AWS only). Drop-in compatible with Redis, no licensing concerns.

Node Types by Provider

ElastiCache node types:

TypeMemoryCost (~)
cache.t3.micro0.5 GiB~$13/mo
cache.t3.small1.4 GiB~$25/mo
cache.t3.medium3.1 GiB~$50/mo
cache.r6g.large13.1 GiB~$130/mo
cache.r6g.xlarge26.3 GiB~$260/mo

Pricing shown next to each type is per node. Multiply by node count for total.

Memorystore tiers:

TierMemoryNotes
M11 GiBBasic
M25 GiBStandard
M316 GiBLarge
M435 GiBExtra Large

Azure Cache for Redis tiers:

TierMemoryNotes
C00.25 GiBBasic
C11 GiBBasic
C22.5 GiBStandard
C36 GiBStandard
P16 GiBPremium (clustering, persistence)

Multi-AZ

When enabled, the cache replicates data across availability zones for automatic failover. If the primary node fails, a replica in another AZ is promoted automatically. This adds ~50% to the cost (replica nodes).

After Provisioning

The cache card in vine detail shows:

  • Primary endpoint — connection string for writes
  • Reader endpoint — connection string for reads (if multi-AZ)
  • Port — typically 6379
  • Status — ACTIVE, CREATING, or FAILED

On this page