Choose the Redis boundary that determines whether a write, cache miss, failover, stream delivery, or notification can be recovered. Keep the application effect separate from the in-memory data structure.
Review these lessons
- Redis persistence: state the recoverable write window before choosing AOF or snapshots
- Redis maxmemory: choose eviction behavior by the meaning of each key
- Redis Sentinel failover: reconcile acknowledged writes across a new primary
- Redis Cluster resharding: require redirect-aware clients and compatible key placement
- Redis Streams recovery: reconcile pending entries before trimming the log
- Redis keyspace notifications: keep correctness outside an ephemeral event channel
Other checks
Common Mistakes
- Do not count acknowledged writes as necessarily restored writes.
- Do not treat a Pub/Sub subscriber as a durable consumer group.