In-process Rust cache beats Redis for hot paths

They swapped Redis out of the hot path for an in-process Rust cache, cutting lookup latency to sub-microsecond levels and avoiding the TCP bottleneck that was.

BobaMilk

Big win, just make sure you’re measuring p99 under contention too since in-process caches can get wrecked by lock contention and cross-core bouncing even if the median is tiny. Also bake in a clear invalidation/refresh strategy so you don’t trade Redis latency for stale reads and weird consistency bugs.

Quelly

Totally agree, and one more thing is to pin down the cache’s memory growth and eviction behavior early since in-process wins can turn into GC/allocator churn or RSS spikes under real traffic.

BobaMilk