Node.js Runtime vs Edge Runtime Tradeoffs

1// app/api/fast-geoip/route.ts
2// 1. EDGE RUNTIME: Boots in sub-5ms across 300+ CDN edge locations
3// Ideal for geolocation, A/B routing, simple token verification
4export const runtime = 'edge';
5
6export async function GET(request: Request) {
7  const geo = request.headers.get('x-vercel-ip-country') ?? 'US';
8  return Response.json({ country: geo });
9}
10
11// ─────────────────────────────────────────────────────────────
12
13// app/api/generate-pdf/route.ts
14// 2. NODE.JS RUNTIME (Default): Full Node.js APIs, filesystem, native C++ addons
15// Ideal for PDF generation, heavy database ORMs, image processing
16export const runtime = 'nodejs'; // or omitted (nodejs is default)
17
18import { db } from '@/lib/db';
19import puppeteer from 'puppeteer-core';
20
21export async function POST(request: Request) {
22  // Safe to use full Node.js ecosystem!
23  return Response.json({ success: true });
24}