Why should a Spring Boot app use ExecutorService instead of new Thread()?
PICTURE THIS: STACK VS QUEUE
Simple meaning
Unbounded new Thread() under load will exhaust memory and file descriptors.
WHY — Concurrency instead of guessing?
Why interviewers care about Concurrency:
on Concurrency.
the situation, the default choice, and one exception - that reads as experience.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Unbounded new Thread() under
load will exhaust memory and file descriptors.
- 2A pool reuses workers,
bounds concurrency, and lets you set a queue and rejection policy.
- 3In Spring you typically
expose a ThreadPoolTaskExecutor bean and pass it to @Async or to CompletableFuture.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Unbounded new Thread() under load will exhaust memory and file descriptors. A pool reuses workers, bounds concurrency, and lets you set a queue and rejection policy.