expertAPI Design, Performance & Resilience

An API works perfectly with 100 concurrent users but times out at 10,000, even though CPU sits at only 40%. Why?

Tests whether you know low CPU with high failure at scale usually points to thread pool or connection pool saturation, not compute.

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

Next Step

Continue to Average API latency is 200ms, but p99 is 8 seconds. What is the real problem, and why does average latency hide it?← Back to all Spring Boot & Microservices questions