Connection pooling in HLD - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use connection pooling in a web application?

Imagine a busy coffee shop where each customer must wait for a new cup to be made before ordering. How does connection pooling help improve efficiency in a similar way for web applications?

A It creates a new connection for every request to ensure freshness.

B It reuses existing connections to reduce the overhead of creating new ones.

C It closes all connections immediately after use to save resources.

D It limits the number of users who can access the application at once.

💡 Hint

Think about how reusing resources can save time and effort.

Connection pooling keeps a set of open connections ready to use, so the application does not need to create a new connection for every request. This saves time and system resources.

❓ Architecture

intermediate

Which component is responsible for managing connection pools in a typical system design?

In a layered system design, where should the connection pool be placed to best serve multiple application requests?

A Within the application server to manage database connections for requests.

B In the network layer to manage all traffic connections.

C On the client side to manage connections to the application server.

D Directly inside the database server to manage client connections.

💡 Hint

Think about where the application talks to the database.

The connection pool is usually managed by the application server because it handles multiple requests that need database access. This allows efficient reuse of database connections.

❓ scaling

advanced

How does connection pooling help scale a high-traffic web application?

Consider a web app receiving thousands of requests per second. How does connection pooling support scaling under this load?

A By creating unlimited new connections for each request to avoid waiting.

B By closing connections immediately after each request to free resources.

C By limiting the number of concurrent connections and reusing them efficiently.

D By distributing requests evenly across multiple databases without pooling.

💡 Hint

Think about resource limits and reuse under heavy load.

Connection pooling limits the number of open connections to a manageable number and reuses them, preventing resource exhaustion and improving response times under heavy traffic.

❓ tradeoff

advanced

What is a tradeoff when using a very large connection pool size?

Increasing the connection pool size seems beneficial. What is a downside of having too many connections open at once?

A It increases resource consumption and can overload the database server.

B It simplifies connection management by avoiding reuse.

C It guarantees no request will ever wait for a connection.

D It reduces latency by always having connections ready.

💡 Hint

Think about system limits and resource usage.

While a large pool reduces waiting time, it consumes more memory and CPU on the database server, which can degrade overall system performance.

❓ estimation

expert

Estimate the maximum number of concurrent requests supported by a connection pool of size 50 if each request holds a connection for 100ms and requests arrive evenly at 10 per second.

Given a connection pool size of 50, each request uses a connection for 100 milliseconds, and requests arrive evenly at 10 per second, what is the maximum number of concurrent requests the system can handle without waiting?

A 100 concurrent requests

B 10 concurrent requests

C 20 concurrent requests

D 50 concurrent requests

💡 Hint

Calculate how many requests can use connections simultaneously based on pool size and request duration.

Each connection can serve 10 requests per second (1000ms / 100ms). With 50 connections, the system can handle 50 concurrent requests at once without waiting.

Practice

1. What is the main purpose of connection pooling in system design?

easy

A. To reuse existing connections and reduce the overhead of creating new ones

B. To create a new connection for every request to ensure freshness

C. To store user data temporarily for faster access

D. To encrypt all data sent between client and server

Solution

1. Step 1: Understand connection creation cost

   Creating new connections for every request is slow and resource-heavy.

2. Step 2: Role of connection pooling

   Connection pooling keeps connections open and reuses them to save time and resources.

3. Final Answer:

   To reuse existing connections and reduce the overhead of creating new ones -> Option A

4. Quick Check:

   Connection pooling = reuse connections [OK]

Hint: Pooling means reuse connections to save time [OK]

Common Mistakes:

• Thinking pooling creates new connections each time
• Confusing pooling with caching user data
• Assuming pooling encrypts data

2. Which of the following is the correct way to configure a connection pool size in a system design?

easy

A. Set pool size to the maximum integer value to allow unlimited connections

B. Set pool size to zero to disable pooling

C. Set pool size to a fixed number based on expected load, e.g., 50

D. Set pool size to negative number to auto-scale connections

Solution

1. Step 1: Understand pool size meaning

   Pool size controls how many connections can be reused simultaneously.

2. Step 2: Choose appropriate pool size

   Setting a fixed number based on expected load balances resource use and performance.

3. Final Answer:

   Set pool size to a fixed number based on expected load, e.g., 50 -> Option C

4. Quick Check:

   Pool size = fixed number for load [OK]

Hint: Pool size should match expected load, not zero or negative [OK]

Common Mistakes:

• Setting pool size to zero disables pooling
• Using negative or unlimited values causes errors
• Ignoring load when setting pool size

3. Consider this pseudocode for connection pooling:

pool = createPool(size=3)
conn1 = pool.getConnection()
conn2 = pool.getConnection()
conn3 = pool.getConnection()
conn4 = pool.getConnection()

What happens when conn4 is requested?

medium

A. conn4 closes one existing connection and reuses it

B. conn4 creates a new connection ignoring the pool size

C. conn4 returns null immediately because pool is full

D. conn4 waits until one connection is released back to the pool

Solution

1. Step 1: Analyze pool size and connections taken

   The pool size is 3, and 3 connections are already taken (conn1, conn2, conn3).

2. Step 2: Behavior on extra connection request

   Requesting conn4 must wait until a connection is released because pool is full.

3. Final Answer:

   conn4 waits until one connection is released back to the pool -> Option D

4. Quick Check:

   Pool full = wait for release [OK]

Hint: Extra requests wait if pool is full [OK]

Common Mistakes:

• Assuming new connections are created beyond pool size
• Expecting null return immediately
• Thinking pool forcibly closes connections

4. A system uses connection pooling but experiences slow responses under high load. Which of the following is the most likely cause?

medium

A. Connections are not reused and closed immediately

B. Pool size is too small, causing requests to wait for connections

C. Pool size is too large, causing too many open connections

D. Timeout settings are too high, causing connections to stay open too long

Solution

1. Step 1: Identify impact of small pool size

   A small pool size means limited connections, so requests wait longer.

2. Step 2: Understand effect on response time

   Waiting for connections causes slow responses under high load.

3. Final Answer:

   Pool size is too small, causing requests to wait for connections -> Option B

4. Quick Check:

   Small pool = slow responses [OK]

Hint: Small pool size causes waiting delays [OK]

Common Mistakes:

• Blaming large pool size for slowness
• Ignoring connection reuse behavior
• Confusing timeout with pool size

5. You design a connection pool for a web service expected to handle 1000 concurrent users. Which combination of settings best balances performance and resource use?

hard

A. Pool size = 100, Timeout = 30 seconds, Max wait time = 10 seconds

B. Pool size = 1000, Timeout = 5 minutes, No max wait time

C. Pool size = 10, Timeout = 1 hour, Max wait time = 1 second

D. Pool size = 5000, Timeout = 10 seconds, No max wait time

Solution

1. Step 1: Evaluate pool size for concurrency

   Pool size of 100 allows many connections but avoids resource overload compared to 1000 or 5000.

2. Step 2: Assess timeout and wait time

   Timeout of 30 seconds frees unused connections quickly; max wait time of 10 seconds prevents long waits.

3. Step 3: Compare other options

   Too large pool sizes waste resources; too small pool or short wait times cause failures.

4. Final Answer:

   Pool size = 100, Timeout = 30 seconds, Max wait time = 10 seconds -> Option A

5. Quick Check:

   Balanced pool size and timeouts = Pool size = 100, Timeout = 30 seconds, Max wait time = 10 seconds [OK]

Hint: Balance pool size and timeouts for best performance [OK]

Common Mistakes:

• Choosing pool size equal to max users wastes resources
• Ignoring max wait time causes request failures
• Setting too long timeout holds connections unnecessarily