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.

Practice

1. What is the main benefit of using connection pooling in a Next.js serverless app?

easy

A. It automatically scales the number of serverless functions.

B. It reuses database connections to improve speed and avoid connection limits.

C. It caches API responses for faster loading.

D. It encrypts database connections for security.

Solution

1. Step 1: Understand connection pooling purpose

   Connection pooling allows reusing existing database connections instead of opening new ones each time.

2. Step 2: Identify benefits in serverless context

   This reuse improves speed and prevents hitting database connection limits common in serverless environments.

3. Final Answer:

   It reuses database connections to improve speed and avoid connection limits. -> Option B

4. Quick Check:

   Connection pooling = reuse connections [OK]

Hint: Pooling means reusing connections to avoid limits [OK]

Common Mistakes:

• Confusing pooling with caching data
• Thinking pooling scales serverless functions
• Assuming pooling encrypts connections

2. Which code snippet correctly creates a MySQL connection pool using mysql2/promise in Next.js?

easy

A. const pool = mysql2.createPool({ host: 'localhost', user: 'root', database: 'test' }).promise();

B. const pool = mysql2.promise.createPool({ host: 'localhost', user: 'root', database: 'test' });

C. const pool = mysql.createPool({ host: 'localhost', user: 'root', database: 'test' });

D. const pool = mysql2/promise.createPool({ host: 'localhost', user: 'root', database: 'test' });

Solution

1. Step 1: Recall mysql2/promise usage

   When importing mysql from 'mysql2/promise', mysql.createPool() directly creates a promise-based pool.

2. Step 2: Match correct syntax

   const pool = mysql.createPool({ host: 'localhost', user: 'root', database: 'test' }); correctly uses the mysql2/promise import.

3. Final Answer:

   const pool = mysql.createPool({ host: 'localhost', user: 'root', database: 'test' }); -> Option C

4. Quick Check:

   mysql2/promise + mysql.createPool() = correct syntax [OK]

Hint: mysql from 'mysql2/promise'; mysql.createPool() [OK]

Common Mistakes:

• Trying to call createPool directly on mysql2/promise import
• Missing .promise() for async support
• Using wrong import or syntax

3. Given this Next.js API handler using a PostgreSQL pool, what will be the output if the database connection fails?

import { Pool } from 'pg';
const pool = new Pool({ connectionString: process.env.DATABASE_URL });

export default async function handler(req, res) {
  try {
    const client = await pool.connect();
    const result = await client.query('SELECT NOW()');
    client.release();
    res.status(200).json({ time: result.rows[0].now });
  } catch (error) {
    res.status(500).json({ error: 'Database connection failed' });
  }
}

medium

A. Returns JSON with error message 'Database connection failed'.

B. Returns empty JSON object {}.

C. Throws an unhandled exception crashing the server.

D. Returns JSON with current time from database.

Solution

1. Step 1: Analyze try-catch behavior

   If pool.connect() fails, the code jumps to the catch block.

2. Step 2: Check catch block response

   The catch block sends a 500 status with JSON error message 'Database connection failed'.

3. Final Answer:

   Returns JSON with error message 'Database connection failed'. -> Option A

4. Quick Check:

   Error caught = JSON error response [OK]

Hint: Errors in try send JSON error response [OK]

Common Mistakes:

• Assuming unhandled exception crashes server
• Expecting successful time JSON on failure
• Thinking empty JSON is returned

4. Identify the bug in this Next.js serverless function using MySQL connection pooling:

import mysql from 'mysql2/promise';
const pool = mysql.createPool({ host: 'localhost', user: 'root', database: 'test' });

export default async function handler(req, res) {
  const connection = await pool.getConnection();
  const [rows] = await connection.query('SELECT * FROM users');
  res.status(200).json(rows);
}

medium

A. Missing connection.release() after query.

B. Using getConnection() instead of connect().

C. Pool should be created inside the handler.

D. Query syntax is incorrect.

Solution

1. Step 1: Check connection usage

   The code gets a connection from the pool but never releases it back.

2. Step 2: Understand pooling best practice

   Connections must be released with connection.release() to avoid leaks and exhaustion.

3. Final Answer:

   Missing connection.release() after query. -> Option A

4. Quick Check:

   Always release pooled connections [OK]

Hint: Always release connections after use [OK]

Common Mistakes:

• Forgetting to release connections
• Thinking getConnection() is invalid
• Creating pool inside handler causing overhead

5. You want to optimize a Next.js serverless app connecting to PostgreSQL with connection pooling. Which approach best prevents exhausting database connections during high traffic?

hard

A. Close the pool after each query to free resources.

B. Create a new pool inside each API handler call.

C. Use a new client connection for every query without pooling.

D. Create a single global pool instance reused across requests.

Solution

1. Step 1: Understand serverless connection challenges

   Serverless functions can run many instances, so creating many pools wastes connections.

2. Step 2: Choose pooling strategy

   Creating a single global pool reused by all handlers limits total connections and improves reuse.

3. Final Answer:

   Create a single global pool instance reused across requests. -> Option D

4. Quick Check:

   Global pool reuse prevents connection exhaustion [OK]

Hint: Use one global pool, not new pools per request [OK]

Common Mistakes:

• Making new pool each request causing connection overload
• Not using pooling at all
• Closing pool too early causing errors