Java: Thread-Per-Request Bottleneck

Thread-per-request can lead to resource exhaustion.

In a thread-per-request model, each incoming request spawns a new thread. As requests increase, system resources can be exhausted, leading to slowdowns or crashes. Imagine an e-commerce site during a sale; if many users try to access the site simultaneously, the server may run out of threads to handle new requests, causing delays or failures.