X'inhu d-differenza bejn ir-runtime ta' Edge u Node.js?

Question

Accepted Answer

Next.js jista' jgħaddi l-kodiċi tas-server f'żewġ runtime. Ir-**runtime Node.js** (default) huwa l-ambjent Node sħiħ; ir-**runtime Edge** huwa ambjent ħafif ibbażat fuq V8 li jjogħobod f'postijiet edge distribwiti globalment qrib lill-utenti.

## Għażla tal-runtime

```ts
// per route handler / page
export const runtime = "edge";   // or "nodejs" (the default)
```

## It-trade-offs

```text
                  Node.js runtime         Edge runtime
────────────────────────────────────────────────────────────────
APIs              full Node (fs, crypto,  Web APIs only (fetch,
                  Buffer, native modules) Request/Response) — limited
npm packages      all                     only those without Node APIs
Cold start        slower, heavier         near-zero, lightweight
Location          regional (one region)   global (near the user)
Latency to user   higher if far away      very low (geo-distributed)
Execution limits  longer, more memory     short CPU time, less memory
Database          direct TCP connections  HTTP-based DBs only (no raw TCP)
```

## Meta tuża Edge

```text
✓ Middleware (auth checks, redirects, geo-routing) — must be fast & global
✓ Simple, latency-sensitive endpoints (personalization, A/B, feature flags)
✓ Reading geolocation/headers to tailor responses
```

Edge jixraq għal **loġika ħafifa li tibbenefika billi tkun viċina lill-user** u minn starts freddi istantanji.

## Meta tuża Node.js

```text
✓ Direct database connections (Prisma over TCP, etc.)
✓ Heavy computation, large dependencies, native modules
✓ Anything using Node-specific APIs (fs, crypto.randomBytes via Node, Buffer)
```

## Eżempju ta' limitazzjoni reali

```ts
export const runtime = "edge";
import fs from "fs";           // ❌ not available on Edge — build/runtime error
import { PrismaClient } from "@prisma/client"; // ⚠️ needs HTTP/data-proxy on Edge
```

Il-ħafna minn il-libreriji popolari (inklużi ORMs li jiftħu sockets DB grezzi) ma jaħdmux fuq Edge mingħajr adaptor ibbażat fuq HTTP — dan huwa pitfall komuni.

## Għaliex dan importanti

L-għażla tal-runtime hija deċiżjoni arkitettonika vera: **Edge** għal loġika veloċi, globali, ħafifa (speċjalment middleware) b'cold starts minimi, **Node.js** għal aċċess API sħiħ, konnessjonijiet DB diretti, u xogħol tqil.

Il-għarfien ta' limitazzjonijiet Edge (Web APIs biss, l-ebda TCP grezz, esekuzzjoni qasira) jipprevjeni l-iżball ta' spiss ta' poġġi kodiċi peżanti tal-database jew dipendenti minn Node fuq runtime li ma jistax jappoġġaha.