read_heavy_api vulnerable to cache

read heavy apiVulnerable Tocache stampede

Source: Workload·Target: Failure Mode

Summary

Read-heavy API workloads are vulnerable to cache stampede when popular cache keys expire under sustained concurrent load, causing all requests to simultaneously miss and query the origin database.

Evidence

·read_heavy_api runs at 10k-50k rps and recommends cache_aside; cache_stampede lists cache_aside in affects_patterns (workloads/read_heavy_api.yaml, failure_modes/cache_stampede.yaml)
·read_heavy_api spike_multiplier 8.0 concentrates concurrent access on hot keys - the >100 req/s hot-key condition cache_stampede requires (workloads/read_heavy_api.yaml)

Evidence grounding

Grounded, 2 supporting items

Read-heavy APIs leaning on cache_aside at high rps hit the hot-key concurrent-miss condition cache stampede requires.