Format: YYYY-MM-DD-description.md - 2026-01-19-infrastructure-deployment.md - 2026-01-19-backend-api-implementation.md (in progress) Co-Authored-By: Claude Sonnet 4.5 (1M context) <noreply@anthropic.com>
39 lines
1.1 KiB
Markdown
39 lines
1.1 KiB
Markdown
---
|
||
title: Prevent Waterfall Chains in API Routes
|
||
impact: CRITICAL
|
||
impactDescription: 2-10× improvement
|
||
tags: api-routes, server-actions, waterfalls, parallelization
|
||
---
|
||
|
||
## Prevent Waterfall Chains in API Routes
|
||
|
||
In API routes and Server Actions, start independent operations immediately, even if you don't await them yet.
|
||
|
||
**Incorrect (config waits for auth, data waits for both):**
|
||
|
||
```typescript
|
||
export async function GET(request: Request) {
|
||
const session = await auth()
|
||
const config = await fetchConfig()
|
||
const data = await fetchData(session.user.id)
|
||
return Response.json({ data, config })
|
||
}
|
||
```
|
||
|
||
**Correct (auth and config start immediately):**
|
||
|
||
```typescript
|
||
export async function GET(request: Request) {
|
||
const sessionPromise = auth()
|
||
const configPromise = fetchConfig()
|
||
const session = await sessionPromise
|
||
const [config, data] = await Promise.all([
|
||
configPromise,
|
||
fetchData(session.user.id)
|
||
])
|
||
return Response.json({ data, config })
|
||
}
|
||
```
|
||
|
||
For operations with more complex dependency chains, use `better-all` to automatically maximize parallelism (see Dependency-Based Parallelization).
|