ARCHITECTURE
Two planes. One sub-millisecond path.
The data plane serves every request from memory. The control plane defines what it does, and can change it in production in seconds. The data plane never blocks on the control plane.
DATA PLANE
The gateway that handles every request.
Stateless, compiled routes held in memory, config read from a local snapshot. If the control plane goes down, the data plane keeps serving.
- Never interprets YAML at request time
- Memory-only hot path, atomic config swap
- Scales horizontally, stateless rolling deploy
P99 OVERHEAD
0.8ms
RPS / CORE
28,400
RAM / 1k ROUTES
142 MB
CONTROL PLANE
The brain that defines what to do.
Routes are authored, validated, versioned, and pushed from here. Changes are git-trackable, peer-reviewable, and rollback-able.
- Declarative routes, YAML or Terraform, versioned in git
- Schema validation + dry-run before publish
- RBAC + audit on every change, 4-eyes approval gates
CONFIG PROPAGATION
< 5s
ROLLBACK
1 click
RESTARTS
0
Life of a request
Everything that happens in 0.84ms.
request · 7c1a4f… · /v2/payments/482200 · 0.84ms
+0.00ms
TLS handshake, client mTLS verified
cert OU=web-checkout
+0.08ms
Auth + scope check
JWT · iss=auth.acme
+0.11ms
WAF, OWASP CRS + custom rules
17 rules · pass
+0.18ms
Transform request, json → soap
declarative map
+0.21ms
Upstream call, SOAP/WSSE
core.internal · 0.46ms
+0.78ms
Transform + redact response
2 fields masked
+0.82ms
Audit log, sha256-chained
block #4,201,884
Want the deep dive?
We'll walk your architects through the planes, the failure modes, and the numbers, on your systems.