Redis in production
Set up Redis for production load: data survives a restart, memory doesn't run out unexpectedly, access is locked down with passwords and TLS, and when the master fails, traffic moves to a replica.
- RESP3: the HELLO handshakeeasy
- Who ate Redis's memoryeasy
- RDB backup with BGSAVEmedium
- AOF that survives a restartmedium
- A cache that never refuses writesmedium
- The slowest command in SLOWLOGmedium
- An ACL user just for the cachemedium
- Close anonymous access to Redismedium
- TLS for Redis with your own CAhard
- A Redis replica on a second portmedium
- Sentinel and a manual failoverhard
- Your own Redis Cluster of three mastershard
- A distributed lock for cron scriptshard
- A consumer group for the orders streammedium
- Reclaim messages from a crashed workermedium
- A JSON document in Rediseasy
- Searching hashes: the Query Enginemedium
- Similar documents: Vector Setsmedium