← Back to docs
Recipe: Timeout budget hierarchy
Every network call in Meridian carries a deadline. This recipe defines the cascading timeout budget from the outermost HTTP request down to individual syscalls.
Budget layers
Client → Vercel edge30 s
Edge → Upstash KV read3 s
Edge → KeyAuth verify5 s
Edge → CDN payload fetch8 s
Loader → Themida unpack12 s
Circuit breaker
If any layer exhausts its budget, the caller propagates a deadline- exceeded signal upward. The edge layer returns HTTP 504 with a signed retry-after header.
retry-after: 2.0
x-deadline-layer: kv-read
x-circuit-state: half-open
x-deadline-layer: kv-read
x-circuit-state: half-open