Edge Cache and CDN Platform  ·  View 07 of 29  ·  3 · Structure

Layered Architecture

Six layers, each depending only on the layers below, with the serving layers reading local files and nothing further away.

Editable source SVG draw.io All views
Steering Anycast prefixes BIRD · 4 classes Katran L4 XDP · QUIC CID aware Authoritative DNS PowerDNS · overrides Edge serving Envoy terminator TLS · token · ceilings Keyspec Rust · one implementation Traffic Server edge RAM + NVMe · peering ring Tag table LMDB · invalidations Shield Traffic Server shield 4 sites · collapse Origin guard ceilings · mTLS PoP autonomy PoP agent verify · apply · ack NATS leaf node local log mirror Local bundles last 5, signed Control plane Config repo Forgejo · CUE Compiler + validator invariants · signing Ring controller Temporal Purge API Go · rate-limited Record and insight Invalidation log JetStream R3 Control DB PostgreSQL · Patroni Delivery analytics Kafka → ClickHouse Audit trail Object Lock · 3 y IPIP miss reads pulls bundles appends Layered Architecture Interface / broker Application we own Decision point Data store Security / platform Queue / topic synchronous event / async Every arrow points down. Serving reads only files on local disk, so nothing below the PoP layer can stop a response. v 1.0 · owner Edge Architecture · date 2026-09

Decisions

  • PoP autonomy is its own layer. The agent, the local log mirror and the last five signed bundles are what let a PoP serve for weeks without the control plane.
  • Keyspec is drawn as a decision, not a component. It is small, it decides whether a stored response may answer a request, and it is the most carefully tested code on the platform.
  • The tag table sits in the serving layer because every lookup reads it. It is written from below by the agent and never by the request path.

The rule these arrows follow

  • Serving depends on local disk. Local disk is filled from the control plane. The control plane writes records. No arrow points up, so the failure of any lower layer beyond the PoP stops change, never delivery.

Omitted

  • Identity, key custody and paging are cross-cutting and are drawn on views 27 and 28.