Problem
One product page has gone viral, now serving 2,000 requests/second at the app tier; a single cache key behind it needs to absorb 150,000 reads/sec. The app tier was sized for ordinary traffic, and Redis isn't yet configured to survive one key this hot, so it's badly over its effective capacity. Resize the fleet, and fix Redis so it can absorb one exceptionally hot key.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.