Connection pooling for serverless in NextJS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use connection pooling in serverless Next.js apps?

In serverless environments like Next.js API routes, why is connection pooling important?

A It reduces the number of database connections by reusing existing ones, improving performance and avoiding connection limits.

B It creates a new database connection for every request to ensure data freshness.

C It caches database queries on the client side to reduce server load.

D It automatically scales the database server horizontally without configuration.

💡 Hint

Think about how serverless functions start and stop frequently and how databases limit connections.

Serverless functions can open many connections quickly, causing limits to be reached. Connection pooling reuses connections, reducing overhead and improving performance.

❓ component_behavior

intermediate

What happens when you don't use connection pooling in Next.js API routes?

Consider a Next.js API route that opens a new database connection on every request without pooling. What is the most likely outcome under heavy traffic?

A The database will reject all queries due to slow network latency.

B The serverless functions will cache connections automatically, so no problem occurs.

C The app will run smoothly with no issues because serverless functions are stateless.

D The database will quickly reach its maximum connection limit, causing errors and failed requests.

💡 Hint

Think about how many connections a database can handle and what happens if too many open at once.

Without pooling, each request opens a new connection. Under heavy load, this exhausts the database's connection limit, causing errors.

📝 Syntax

advanced

Identify the correct way to implement connection pooling in a Next.js API route

Which code snippet correctly implements connection pooling using a global variable to reuse a single database client instance in Next.js API routes?

NextJS

import { Client } from 'pg';

let client;

export default async function handler(req, res) {
  if (!client) {
    client = new Client({ connectionString: process.env.DATABASE_URL });
    await client.connect();
  }
  const result = await client.query('SELECT NOW()');
  res.status(200).json({ time: result.rows[0].now });
}

A The code creates a new client on every request without reusing, causing connection overload.

B The code correctly reuses the client connection across requests by storing it in a global variable.

C The code uses a client but never calls connect(), so queries will fail.

D The code closes the client after each request, preventing reuse.

💡 Hint

Look for where the client is created and if it is reused across requests.

Storing the client in a global variable and connecting once allows reuse across serverless invocations, implementing pooling.

🔧 Debug

advanced

Why does this Next.js API route cause 'too many clients' error?

Given this code, why might the app throw a 'too many clients' error under load?

NextJS

import { Pool } from 'pg';

export default async function handler(req, res) {
  const pool = new Pool({ connectionString: process.env.DATABASE_URL });
  const client = await pool.connect();
  const result = await client.query('SELECT NOW()');
  client.release();
  res.status(200).json({ time: result.rows[0].now });
}

A The environment variable DATABASE_URL is missing, causing connection failures.

B The query syntax is incorrect, causing the database to reject connections.

C A new Pool instance is created on every request, so connections are not reused, causing overload.

D The client is never released back to the pool, causing connection leaks.

💡 Hint

Check where the Pool is created and how often.

Creating a new Pool on every request defeats pooling because each pool manages its own connections, quickly exhausting limits.

❓ state_output

expert

What is the output of this Next.js API route with connection pooling under concurrent requests?

Consider this Next.js API route code. What will be the output when 3 requests arrive almost simultaneously?

NextJS

import { Pool } from 'pg';

const pool = new Pool({ connectionString: process.env.DATABASE_URL, max: 2 });

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

A Two requests will complete after about 1 second; the third will wait for a connection and complete after about 2 seconds.

B All three requests will complete simultaneously after 1 second because the pool allows unlimited connections.

C The third request will fail immediately with a connection error because the pool max is 2.

D All requests will fail because pg_sleep is not supported in queries.

💡 Hint

Think about the pool max connections and how pg_sleep delays queries.

The pool allows only 2 connections. Two requests use them and sleep 1 second. The third waits for a free connection, so it finishes after about 2 seconds.