Database
Redis development
How does AonHive use Redis?
Redis development for queues, cache, and session state.
Redis holds what can be rebuilt: a cache, a queue, a lock that lasts for one operation, a rate limit. The database holds the ride, the order, and the ledger. A flush of Redis is an inconvenience. It is not data loss.Discuss this stackHow we use it
Fast memory. Not the record.
- 01
Give the cache a way to die
A TTL, and a write that deletes the key. A cache without an invalidation is a second source of truth that nobody admitted.
- 02
Use a lock for the critical section
A payout or a single-flight job takes a short lock. The lock expires. The database condition is still what decides whether the write lands.
- 03
Keep the queue inspectable
A failed job stays visible. Retry has a ceiling. A queue that only grows is an incident, and someone can see it.
Redis
Bring the system this has to fit.
Tell us the product, the estate you already run, and what your team needs to own. We will say whether this belongs in the stack.