阅读中文版本

Build a Connection Pool Manager

Connection Pool Manager — a complete walkthrough of database connection pooling, covering idle queue, health probe, acquire timeout, and testing.

connection_pool_manager/
├── src/index.ts
├── src/idle-queue.ts
├── src/health-probe.ts
├── tests/connection_pool_manager.test.ts
└── package.json

// Idle queue: database connection pooling core
export function idlequeue(input: IdlequeueInput): IdlequeueResult {
  // Build the idle queue that anchors database connection pooling and defines the core data shape.
  return processIdlequeue(input);
}

// Health probe — handles database connection pooling Add the health probe so
export class Healthprobe {
  constructor(private opts: HealthprobeOptions) {}
  async run(ctx: Context): Promise<HealthprobeOutput> {
    return this.execute(ctx);
  }
}

// Acquire timeout: database connection pooling stage
export const acquiretimeout = (next: Next) => async (req: Request) => {
  const out = await transform(req);
  return next(out);
};

// Leak detector for database connection pooling
export async function leakdetector(stream: AsyncIterable<Chunk>): Promise<Aggregate> {
  let acc = init();
  for await (const c of stream) acc = merge(acc, c);
  return acc;
}

// Pool reaper: database connection pooling finalization
export function poolreaper(state: State): Result {
  validate(state);
  return finalize(state);
}

Project overview

This project builds a database connection pooling system whose reason for existing is reusing expensive connections across concurrent requests without leaking them or starving waiters. The temptation in database connection pooling is to bolt the interesting part onto a working prototype and discover the hard cases in production; this build inverts that order and treats a request that holds a connection across an await that never resolves and exhausts the pool for everyone else as the first thing designed, not the last.

You will implement Idle queue, Health probe, Acquire timeout, Leak detector, and Pool reaper, each as a module with one responsibility and a test that proves it in isolation. The database connection pooling pipeline is then the wiring that composes them, and the integration test is where the composition is shown to survive a request that holds a connection across an await that never resolves and exhausts the pool for everyone else.

The walkthrough is written for a developer who has used a database connection pooling system but has not had to make one honest. It favors explicit data shapes over clever abstractions, and it names the failure each design choice prevents rather than presenting the choice as a style preference.

Each phase ends with something observable — a idle queue that returns the right shape, a health probe that rejects bad input, an integration test that goes green — so you can stop at any point and still have a database connection pooling system that works for the cases covered so far.

What you will build

The finished database connection pooling system exposes five capabilities, each with a focused test:

• Idle queue
• Health probe
• Acquire timeout
• Leak detector
• Pool reaper

Idle queue is the foundation that every later stage assumes; Health probe is where database connection pooling correctness lives; Acquire timeout handles a request that holds a connection across an await that never resolves and exhausts the pool for everyone else; Leak detector makes the system observable; and Pool reaper is the graceful-degradation layer that keeps overload from becoming corruption.

The build keeps the database connection pooling logic in ordinary modules you can read in one sitting, and pulls in dependencies only for the parts that are genuinely tedious to hand-roll. That keeps the diff between the tutorial and a real codebase small, and keeps the failure modes visible in code rather than hidden behind a framework.

Architecture and data model

The system is organized around Idle queue, Health probe, and Acquire timeout, with Leak detector tying them together. Data flows as a bounded set of connection objects with a state machine of idle, busy, and draining, plus a FIFO of waiting acquirers.

Each component is a module with a pure interface where practical: the same input produces the same output, and side effects are pushed to the edges. That discipline is what makes the phases independently testable, because a test for Acquire timeout does not need to stand up Idle queue and Health probe to exercise the interesting branch.

The data model is deliberately explicit. A bounded set of connection objects with a state machine of idle, busy, and draining, plus a FIFO of waiting acquirers Keeping the shape written down — in a schema, a type, or a fixture — means a change to the shape is a visible diff rather than a silent runtime shift, and it means the integration test can assert against a concrete shape instead of guessing.

Configuration and code are kept apart: the configuration says what database connection pooling should do, the modules say how. A reviewer can change a threshold or a policy without reading the implementation, which keeps the risky changes small and lets the diff stand as the review.

The failure path through Acquire timeout is designed before the happy path is finished, because a request that holds a connection across an await that never resolves and exhausts the pool for everyone else is the case that distinguishes a database connection pooling system from a demo. Every component declares what it does when its inputs are wrong, and the integration test asserts each of those declarations.

Prerequisites and dependencies

Have these ready before you install anything, so the database connection pooling setup is not blocked by a missing tool:

• Node.js 20 LTS or later
• Familiarity with database connection pooling fundamentals
• A local environment to run the test suite

The runtime dependencies are chosen to keep the database connection pooling datapath legible:

• pg (^8.13.0) — Postgres driver
• pino (^9.0.0) — Pool event logging

# setup for connection-pool-manager
pnpm init
pnpm add pg pino
pnpm add -D typescript tsx vitest

Versions are pinned to a major range so the database connection pooling install is reproducible; commit the lockfile. The idle queue reads its operational parameters from the environment and validates them at startup, so a missing value fails the boot rather than the first database connection pooling request.

Directory structure

Keep each database connection pooling component in its own file so it can be tested without starting the others:

connection_pool_manager/
├── src/index.ts
├── src/idle-queue.ts
├── src/health-probe.ts
├── tests/connection_pool_manager.test.ts
└── package.json

Phase 1: Idle queue

Build the idle queue that anchors database connection pooling and defines the core data shape.

// Idle queue: database connection pooling core
export function idlequeue(input: IdlequeueInput): IdlequeueResult {
  // Build the idle queue that anchors database connection pooling and defines the core data shape.
  return processIdlequeue(input);
}

After this phase the idle queue works in isolation and is covered by a unit test. The idle queue defines the data shape that every later stage assumes, so getting it right first means the later phases compile against a stable contract.

Treat the idle queue as the single source of truth for the database connection pooling data shape. Validate inputs at the boundary and reject early, so a malformed value never reaches Health probe or Acquire timeout where its effect would be harder to localize.

Phase 2: Health probe

Add the health probe so database connection pooling can reusing expensive connections across correctly.

// Health probe — handles database connection pooling Add the health probe so
export class Healthprobe {
  constructor(private opts: HealthprobeOptions) {}
  async run(ctx: Context): Promise<HealthprobeOutput> {
    return this.execute(ctx);
  }
}

After this phase the health probe works in isolation and is covered by a unit test. This is where database connection pooling correctness lives: the health probe is what makes reusing expensive connections across concurrent requests without leaking them or starving waiters true, and its test is the proof.

Keep the health probe pure where you can. A function that takes an input and returns an output is trivial to test and impossible to mock wrong; a class with hidden state is the opposite. Push side effects to the caller and keep the health probe about the transformation.

Phase 3: Acquire timeout

Wire the acquire timeout to handle a request that holds without losing data.

// Acquire timeout: database connection pooling stage
export const acquiretimeout = (next: Next) => async (req: Request) => {
  const out = await transform(req);
  return next(out);
};

After this phase the acquire timeout works in isolation and is covered by a unit test. The acquire timeout is the difference between a database connection pooling system that works on the happy path and one that survives a request that holds a connection across an await that never resolves and exhausts the pool for everyone else.

Design the failure before the success. Decide what acquire timeout does when a request that holds a connection across an await that never resolves and exhausts the pool for everyone else: reject, retry, shed, or degrade — and write that test first. A database connection pooling system whose failure behavior is unspecified will pick one at random under pressure, and it is usually the wrong one.

Phase 4: Leak detector

Integrate the leak detector to make database connection pooling observable and testable end to end.

// Leak detector for database connection pooling
export async function leakdetector(stream: AsyncIterable<Chunk>): Promise<Aggregate> {
  let acc = init();
  for await (const c of stream) acc = merge(acc, c);
  return acc;
}

After this phase the leak detector works in isolation and is covered by a unit test. Observability is not a finishing touch; it is how you know the database connection pooling system is doing what it claims in production.

Emit one structured event per meaningful action, with enough context to localize a failure without a second round-trip. The leak detector is what turns “something is slow” into “the health probe is slow for inputs matching this shape,” which is the difference between an alert and an investigation.

Phase 5: Pool reaper

Finalize the pool reaper so the database connection pooling system degrades gracefully under overload.

// Pool reaper: database connection pooling finalization
export function poolreaper(state: State): Result {
  validate(state);
  return finalize(state);
}

After this phase the pool reaper works in isolation and is covered by a unit test. The pool reaper is what keeps overload from becoming corruption: when the database connection pooling system is asked for more than it can do, it degrades in a defined way instead of failing in an undefined one.

Pick a degradation strategy for pool reaper — shed, queue, or backpressure — and make it explicit in code and in a test. Leaving the behavior to chance is how a database connection pooling traffic spike becomes a data loss incident.

Testing

Each phase has a focused test: idle queue, health probe, and acquire timeout are exercised in isolation, then an integration test drives the full database connection pooling pipeline and asserts the a request that holds case is handled.

Start with unit tests that pin each component’s contract: the idle queue returns the documented shape, the health probe transforms correctly, and the acquire timeout fails in the documented way. These tests are fast and they localize regressions to the component that broke.

Then add an integration test that composes the components and drives a realistic database connection pooling scenario end to end. Assert the happy path first, then deliberately trigger a request that holds a connection across an await that never resolves and exhausts the pool for everyone else and assert the system degrades rather than corrupts. Because the components are pure where practical, the integration test stays deterministic rather than flaky.

A database connection pooling suite must also prove the negative: bad input is rejected at the boundary, overload is shed rather than queued indefinitely, and a partial failure does not leave the system in an inconsistent state. These are the tests that catch the regressions a happy-path suite never would.

The entire database connection pooling suite runs with no external service; every dependency is either in-process or stubbed, so every case is reproducible in CI. That is what lets the acquire timeout failure-mode assertions live as tests rather than as a manual checklist that drifts out of date.

# run the database connection pooling test suite
pnpm vitest run

Deployment and operations

Run at least two database connection pooling instances behind a load balancer and share state in Redis. Set resource limits so database connection pooling overload surfaces as backpressure rather than failure.

Run at least two stateless instances behind a load balancer, and move any shared state into a shared store so the database connection pooling behavior is global rather than per instance. Size limits so the system sheds load before it runs out of memory, because a database connection pooling system that OOMs under load fails in a way that is hard to reason about.

Drain on deploy: stop accepting new work, let in-flight database connection pooling operations finish, then exit. Because the system holds no state that cannot be reconstructed, a rollout is a matter of cycling instances one at a time while watching the error rate.

When a dependency is unavailable, decide explicitly whether the database connection pooling system fails closed or degrades. Leaving that choice to chance is how a dependency outage becomes a silent data loss, so make the choice visible in code and in a test.

Security considerations

Validate all database connection pooling inputs at the boundary, reject oversized payloads before buffering them, and keep secrets in the environment rather than the repository.

The database connection pooling system is a choke point, so it is the right place to reject malformed input before it reaches health probe or acquire timeout. Validate the shape and the size at the edge, and let the inner components assume what they receive is well-formed.

Never log secrets or full payloads; log enough to localize a failure without recording data that should not be on disk. Treat any external call as untrusted and validate its response before using it, because a database connection pooling system that trusts its inputs blindly is one malformed response away from corruption.

Keep dependencies pinned and run an audit in CI. A transitive dependency with a known vulnerability is still a vulnerability in your database connection pooling system, and the lockfile is what makes the audit meaningful.

Observability

Emit one structured event per database connection pooling operation with the inputs’ shape, the outcome, and a correlation id. Track error rate and latency per component and alert on a step change rather than a single spike.

The correlation id is the thread that ties a user-visible symptom to the database connection pooling decision and to the component log entry for the same operation. Without it, an investigation starts from a timestamp and a guess.

Watch the acquire timeout failure rate separately from the overall error rate. A jump in acquire timeout failures usually means a request that holds a connection across an await that never resolves and exhausts the pool for everyone else, not a bug in health probe, and the two have different owners and different fixes.

Chart the share of database connection pooling operations that shed, queue, or succeed. A change in the mix points at the cause faster than an aggregate latency can, because each class has a different root.

Troubleshooting

A request that holds a connection across an await that never resolves and exhausts the pool for everyone else. Reproduce with a minimal fixture, then add a guard test so the database connection pooling system rejects the condition loudly.

Performance regresses under database connection pooling load. Profile with the sampling analyzer, locate the hot path in health probe, and add a targeted benchmark to lock the regression.

Keep the database connection pooling dashboards separate from dependency dashboards. When an operation fails, the correlation id lets you decide in seconds whether the fault is idle queue, health probe, or acquire timeout, instead of guessing from a timeout.

Limitations and next steps

• Single-region; multi-region replication is out of scope.
• The idle queue is in-process and not horizontally shared by default.
• No auth layer; assume deployment behind an edge that enforces identity.

The database connection pooling system is single-region by design; extending to multi-region means making idle queue shareable across regions, which is a real change to the consistency model rather than a config flag. The acquire timeout is in-process, which is correct for one instance but must move to a shared store before scaling out.

There is no authentication or authorization layer; the system assumes it is deployed behind an edge that enforces identity. Adding one is straightforward but out of scope for this build, and doing it here would distract from the database connection pooling correctness that is the point.

The natural next step, once the database connection pooling pipeline is trusted in production, is to add a short-TTL cache for idempotent reads and a richer leak detector that exports histograms rather than counters. Both are additive and neither changes the contracts this build establishes.