How do you reason about pool size versus Tomcat threads?
PICTURE THIS: DATABASE INDEX
Simple meaning
Each request thread that hits the database needs a connection at the same time.
WHY — Connection pooling instead of guessing?
Why interviewers care about Connection pooling:
contrast on Connection pooling, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
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:
- 1Each request thread that
hits the database needs a connection at the same time.
- 2If you have 200
Tomcat threads and a pool of 10, 190 threads may block on the pool.
- 3Either reduce servlet threads,
make work async, or raise the pool only as far as the database can handle.
- 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
Each request thread that hits the database needs a connection at the same time. If you have 200 Tomcat threads and a pool of 10, 190 threads may block on the pool.