Problem
Paradox Shop's storefront serves 1,000 requests/second and caches every page with the same fixed TTL, all written around the same time each day; at midnight, that means roughly 20,000 keys will expire within the same second, each one risking a flood of concurrent database reads all at once. Build the app tier and a cache that survives a synchronized mass expiry without hammering the database.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.