Database migrations in NextJS - Performance & Optimization

Performance: Database migrations

MEDIUM IMPACT

Database migrations affect the backend deployment speed and can indirectly impact frontend load times if migrations block API responses.

Applying database schema changes during app startup

NextJS

import { migrate } from 'some-migration-lib';

// Run migrations once during deployment or startup, not per request
await migrate();

export async function getServerSideProps() {
  return { props: {} };
}

Migrations run once upfront, so requests are fast and non-blocking.

📈 Performance Gainreduces request blocking to near zero, improving response time

Applying database schema changes during app startup

NextJS

import { migrate } from 'some-migration-lib';

export async function getServerSideProps() {
  await migrate(); // runs migrations on every request
  return { props: {} };
}

Running migrations on every server request blocks response and increases latency.

📉 Performance Costblocks rendering for 100-500ms per request depending on migration size

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Run migrations on every request	N/A	N/A	Blocks frontend rendering due to slow API	[X] Bad
Run migrations once during deployment	N/A	N/A	Fast API responses, smooth frontend rendering	[OK] Good
Run large migrations synchronously in API	N/A	N/A	Blocks API response, causes slow interaction	[X] Bad
Run large migrations asynchronously in background	N/A	N/A	Non-blocking API, fast user interaction	[OK] Good

Rendering Pipeline

Database migrations run on the backend and can delay server responses that frontend depends on, indirectly affecting rendering speed.

→Server Response Time

→Data Fetching

→Frontend Rendering

⚠️ BottleneckServer Response Time when migrations run synchronously

Optimization Tips

1Run database migrations during deployment, not on user requests.

2Avoid synchronous migrations in API handlers to prevent blocking responses.

3Use background jobs or async triggers for large migrations to keep frontend responsive.

Performance Quiz - 3 Questions

What is the main performance risk of running database migrations during every frontend request?

A It causes layout shifts on the page

B It increases CSS paint cost

C It blocks server response, increasing frontend load time

D It reduces JavaScript bundle size

DevTools: Performance

How to check: Record a server response timeline while triggering API calls that run migrations; look for long blocking times.

What to look for: Long server blocking times or delayed API responses indicate migration blocking.