Edge runtime
Runtime characteristics of CepatEdge on Cloudflare Workers and Durable Objects.
Workers
| Aspect | Characteristic |
|---|---|
| Engine | V8 (Workers runtime) |
| Memory | Per-request isolate limits (platform-defined) |
| CPU / wall time | Platform CPU and wall-time budgets per request |
| Model | Isolated execution per request |
| Distribution | Global edge network |
Durable Objects
| Aspect | Characteristic |
|---|---|
| State | Persistent across requests for a given object id |
| Consistency | Strong within an object |
| Storage | SQLite-backed DO storage |
| Scaling | One active instance per object id / namespace |
Used for sessions, cache namespaces, and log shards — see cache and logs.
Configuration
- Bindings: Workers env (DOs, R2, vars)
- Secrets: Encrypted secrets (DB URL, JWT, mailer, OIDC, …)
- Docs: Configuration guide · Domains
Performance envelope (targets)
| Path | Target |
|---|---|
| Edge processing | <10ms typical |
| Cache hits | <5ms typical |
| DB (uncached) | <50ms with pooling |
| Global user-perceived | <100ms P95 where cache-first |
Scaling is automatic at the edge; DO namespaces keep hot state without cold-start session loss for those objects.