# Next.js

> Server rendering and incremental static regeneration: pages earn 50% more, at 1.6× their CPU, and a CDN can answer 40% of them. 30 MB per process.

## Trade-offs

| Axis | Score |
| --- | --- |
| Throughput | |
| Tail latency | |
| Memory | |
| Velocity | |
| Resilience | |
| Operability | |

## Runs on

- [Node.js](https://wiki.playquorum.dev/runtimes/node.md)
- [Node.js cluster](https://wiki.playquorum.dev/runtimes/node_cluster.md)
- [Bun](https://wiki.playquorum.dev/runtimes/bun.md)
- [Deno](https://wiki.playquorum.dev/runtimes/deno.md)

## Engineering terms

- [CDN (content delivery network)](https://wiki.playquorum.dev/glossary/cdn-content-delivery-network.md)

## Facts

Next.js
- **Language:** Node.js
- **Overhead:** 1 ms CPU
- **Velocity:** ×1.35
- **Memory:** +30 MB
- **Startup:** +0 s
- **ORM:** No

## See also

- [Runtimes and frameworks](https://wiki.playquorum.dev/runtimes.md)

Source: https://wiki.playquorum.dev/frameworks/nextjs