Connection pooling in HLD - System Design Guide

Problem Statement

Opening a new database connection for every request causes high latency and resource exhaustion. When many clients connect simultaneously, the database server can become overwhelmed, leading to slow responses and potential crashes.

Solution

Connection pooling keeps a set of open database connections ready to use. When a request needs a connection, it borrows one from the pool instead of opening a new one. After use, the connection is returned to the pool for reuse, reducing overhead and improving performance.

Architecture

Application

Server

→Connection

↓

Database

Database

This diagram shows the application server borrowing and returning connections from the connection pool, which manages open connections to the database server.

Trade-offs

✓ Pros

→

Reduces latency by reusing existing connections instead of opening new ones.

→

Lowers resource consumption on the database server by limiting concurrent connections.

→

Improves throughput under high load by managing connection reuse efficiently.

✗ Cons

→

Requires careful configuration of pool size to avoid connection starvation or resource waste.

→

Idle connections in the pool may consume resources unnecessarily if not managed properly.

→

Complexity increases with handling connection leaks and stale connections.

Use when your application makes frequent database requests and opening new connections is costly, typically at scales above hundreds of requests per second.

Avoid when your application has very low database traffic (under 10 requests per second) or when the database driver already manages connections efficiently without pooling.

Real World Examples

Netflix

Netflix uses connection pooling to handle millions of streaming metadata requests efficiently without overwhelming their databases.

Uber

Uber employs connection pooling to maintain fast response times for ride requests by reusing database connections across their microservices.

Shopify

Shopify uses connection pooling to scale their e-commerce platform, reducing latency during peak shopping periods.

Alternatives

Database Proxy

Acts as an intermediary managing connections and routing queries, often providing pooling as a service outside the application.

Use when: Choose when you want centralized connection management across multiple applications or services.

Serverless Database Connections

Uses ephemeral connections managed by serverless platforms, avoiding persistent pools but potentially increasing connection overhead.

Use when: Choose when using serverless architectures where persistent connections are not feasible.

Summary

Connection pooling improves performance by reusing database connections instead of opening new ones for each request.

It reduces resource usage on the database server and lowers latency under high load.

Proper configuration and management of the pool size are critical to avoid resource waste or connection starvation.

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