Connection pooling for serverless in NextJS - Performance & Optimization

Performance: Connection pooling for serverless

HIGH IMPACT

This affects backend response time and serverless function cold start latency by managing database connections efficiently.

Managing database connections in serverless Next.js API routes

NextJS

import { MongoClient } from 'mongodb';

let cachedClient = null;
let cachedDb = null;

export default async function handler(req, res) {
  if (!cachedClient) {
    cachedClient = await MongoClient.connect(process.env.MONGO_URI);
    cachedDb = cachedClient.db();
  }
  const data = await cachedDb.collection('items').find().toArray();
  res.json(data);
}

Reuses a cached database connection across invocations, reducing connection overhead and latency.

📈 Performance GainReduces cold start delay by 100-300ms and improves INP by faster response times.

Managing database connections in serverless Next.js API routes

NextJS

export default async function handler(req, res) {
  const client = await MongoClient.connect(process.env.MONGO_URI);
  const db = client.db();
  const data = await db.collection('items').find().toArray();
  await client.close();
  res.json(data);
}

Opening and closing a new database connection on every request causes high latency and resource waste.

📉 Performance CostBlocks response for 100-300ms per request, increasing cold start time and INP.

Performance Comparison

Pattern	Connection Setup	Latency Impact	Resource Usage	Verdict
Open/close connection per request	New connection every time	High latency (100-300ms delay)	High CPU and memory usage	[X] Bad
Cached connection pooling	Single connection reused	Low latency (minimal delay)	Low resource usage	[OK] Good

Rendering Pipeline

Connection pooling reduces backend processing time, allowing faster serverless function execution and quicker response delivery to the browser.

→Serverless Function Execution

→Network Response

⚠️ BottleneckBackend connection setup and teardown

Core Web Vital Affected

INP

This affects backend response time and serverless function cold start latency by managing database connections efficiently.

Optimization Tips

1Cache database connections outside the serverless handler to reuse them.

2Avoid opening and closing connections on every request to reduce latency.

3Monitor API response times to detect connection overhead issues.

Performance Quiz - 3 Questions

What is the main performance benefit of connection pooling in serverless functions?

A Reduces database connection overhead and speeds up response times

B Increases the number of database connections opened

C Blocks rendering on the client side

D Improves CSS paint performance

DevTools: Network and Performance panels

How to check: Use Network panel to measure API response times; use Performance panel to record serverless function cold start delays.

What to look for: Look for long initial API response times indicating connection overhead; shorter times indicate effective pooling.