Design the container orchestration and scaling strategy for an e-commerce platform that sees 50x traffic spikes during flash sales.
Cover: horizontal autoscaling (HPA or equivalent) tuned with appropriate scale-up aggressiveness and scale-down caution to avoid flapping; pre-warming capacity ahead of known sale start times rather than relying solely on reactive autoscaling (cold-start lag matters at 50x spikes); stateless service design so scaling is just adding replicas; a database/cache layer designed for the read-heavy spike pattern (read replicas, aggressive caching, possibly a queue to smooth write bursts for order processing); and explicit load-shedding/graceful-degradation behavior (e.g., disabling non-critical featu
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response