workerd Request Lifecycle
How an HTTP request flows through V8 isolates, capability bindings, and nanoservice routing
Single Worker Request
Nanoservice Chain
Reset
HTTP
Route
Dispatch
fetch()
env.AUTH
Response
Same thread, zero latency
Client
HTTP request
workerd Server
C++ / Cap'n Proto
Cap. Router
Bindings config
V8 Isolate
Worker A
fetch() handler
env bindings
KV / R2
External binding
Auth Worker
Nanoservice
# workerd.capnp
const config :Workerd.Config
= (
services
= [(
name
=
"main"
,
worker
= (
compatibilityDate
=
"2026-03-17"
,
bindings
= [(
name
=
"AUTH"
,
service
=
"auth"
)]))]
Interactive Diagram:
Hover over components to see details, or use the buttons above to trace request flows.