Warm Functions

Edge functions kept warm against cold-start latency. List is hardcoded today (3 places: infrastructure/scripts/warmup.sh, apps/sale/services/userIsolateWarmer.ts, infra-api/src/routes/stubs.js). Toggle column is a placeholder — wiring lives in the next iteration (DB-backed config).

Total in warm list

Currently enabled

P0 (per-sale critical)

How this list is used

Server-side warmup ( evrenos-warmup.timer on the EC2 host) pings each function with X-Warmup: 1 on the configured cadence. Edge functions short-circuit on that header (HTTP 204) so the warmup itself costs nothing beyond keeping the isolate hot.

Client-side per-user warmup (userIsolateWarmer.ts) fires the same list against the cashier's JWT every 60 s while their session is active. Per-user isolates are separate from anon-warmup ones — both are needed.

EDGE_MEM budget rule: list length must stay below (EDGE_MEM_MB / 128) - 2. At 2 048 MiB that ceiling is 14; we are at 7 — plenty of headroom for burst cold-starts.

When you change this list: update all three files identically. Drift between server and client warmup creates cold-start asymmetry that's painful to debug from the dashboard.