How do you size JDBC pool, Tomcat threads, and Kafka consumer concurrency together?
PICTURE THIS: DATA SPLIT
Fit on train, tune on val, report on test once.
Simple meaning
The tightest downstream resource wins.
WHY — Connection pooling instead of guessing?
Why interviewers care about Connection pooling:
question about Connection pooling.
trade-offs, and what you would actually do on a Backend project - not buzzwords.
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:
- 1Define it
The tightest downstream resource wins.
- 2If Postgres allows 100
connections and you have 4 pods, each pool might be 20 plus headroom for migrations and admin.
- 3Tomcat threads should not
greatly exceed what those connections plus CPU can usefully run, and Kafka concurrency must not multiply extra DB sessions per message.
- 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
The tightest downstream resource wins. If Postgres allows 100 connections and you have 4 pods, each pool might be 20 plus headroom for migrations and admin.