Why this matters
- VaultCommerce's Redis footprint grew past 32 GB of hot keys — Cluster spreads slots across nodes; Sentinel alone cannot shard.
- Hot keys (a viral SKU counter) saturate one slot even in Cluster — application-level sharding or local caching still matters.
- Production hardening spans TLS, ACLs, memory limits, and slow-log monitoring — not just topology choice.
Cluster
Node 1Shard 0 primary
Node 2Shard 1 primary
Node 3Shard 0 replica
Primary-replica with Sentinel
One primary accepts writes; replicas serve reads and stand by for promotion. Three or more Sentinel processes quorum-vote on failures.
# sentinel.conf
sentinel monitor vaultcommerce-redis 10.0.1.10 6379 2
sentinel down-after-milliseconds vaultcommerce-redis 5000
sentinel failover-timeout vaultcommerce-redis 60000
SENTINEL masters
SENTINEL replicas vaultcommerce-redis
SENTINEL get-master-addr-by-name vaultcommerce-redis
Clients must resolve the current primary after failover — use a Sentinel-aware driver or managed endpoint.
Sentinel vs Cluster
- Sentinel — HA for a single dataset; one primary at a time; simpler ops.
- Cluster — 16,384 hash slots sharded across primaries; multi-master writes.
- Both — use replicas for read scaling; Cluster adds slot migration for growth.
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 3 sections
- Redis Cluster essentials
- Hot-key mitigation
- Production checklist
Test yourself
Answer these before moving on — recall is what makes it stick.