InMemory Redis Memcached
Fast key-value caching for hot data — session state, computed aggregates, rate-limit counters.
Why we need this / what value this brings
Sub-millisecond reads for hot data that would otherwise mean a DB round-trip on every request.
When to use this
Frequently-read, computed, or session-scoped data where a DB query is disproportionately expensive relative to how often the underlying data changes.
How to use or implement this
Cache-aside is the simplest pattern: check cache, on miss read from DB and populate cache, set a TTL matched to how stale is acceptable.
Research questions
- Does Localz have a Redis instance yet, and what's the first thing worth caching (provider availability lookups)?
Empty folder — drop notes, links, and findings here as you research.