Why does a Java service use a JDBC connection pool instead of DriverManager.getConnection per request?
PICTURE THIS: A REST CALL
Simple meaning
Opening a TCP connection and authenticating to Postgres on every HTTP call is slow and will exhaust database max_connections.
WHY — Connection pooling instead of guessing?
Why interviewers care about Connection pooling:
on Connection pooling.
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:
- 1Opening a TCP connection
and authenticating to Postgres on every HTTP call is slow and will exhaust database max_connections.
- 2A pool keeps warm
connections and hands them out for the duration of a transaction.
- 3You size the pool
to the database, not to the Tomcat thread count blindly.
- 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
Opening a TCP connection and authenticating to Postgres on every HTTP call is slow and will exhaust database max_connections. A pool keeps warm connections and hands them out for the duration of a transaction.