Edge Cache and CDN Platform  ·  View 11 of 29  ·  4 · Data

Four Data Classes, Designed Separately

Cached content, configuration, invalidation state and telemetry each get their own store, their own replication and their own recovery objective.

Editable source SVG draw.io All views
Cached content · derived, disposable RAM cache hot working set NVMe cache LUKS2 · per-property volumes Negative cache 404 · 410 · short TTL Configuration · authoritative, versioned Config repo Forgejo · signed commits Bundle store Ceph RGW · by hash Local bundles last 5 on every PoP Invalidation state · ordered, never lost Invalidation log JetStream R3 · 30 days PoP mirrors one per PoP Tag tables LMDB per node Telemetry · very large, droppable Access records Kafka · 3 days Hot logs ClickHouse · 30 days Cold logs Parquet · 400 days Audit trail Object Lock · 3 years compile pull mirror apply TTL move Four Data Classes, Designed Separately Data store Queue / topic synchronous event / async batch Recovery objectives: content none · configuration RPO 5 min · invalidation RPO 0 · telemetry best effort. v 1.0 · owner Edge Architecture · date 2026-09

Why four

  • Cached content has no recovery objective. Losing a PoP's cache costs money and latency, never data, which is why eighteen unattended sites are affordable.
  • Invalidation state is small and must not be lost, the opposite of the cache it governs. It gets consensus replication across three sites and a local mirror at each PoP.
  • Telemetry is the largest class and the least important to the serving path. It is allowed to drop, and the drop is counted.

Numbers

  • About 150 TB of distinct cacheable bytes across 900 million objects; each tier-1 PoP holds about 370 TB of raw NVMe and each edge-only PoP about 90 TB, so no single PoP needs the whole population.
  • Access logs 30 days hot and 400 days cold; invalidation and configuration audit 3 years; aggregated delivery metrics 13 months.

Assumptions

  • The longest tolerated PoP absence is 14 days, and the invalidation log is retained for 30. A PoP away longer discards its key space logically instead of replaying (view 17).
◀  Integration Surface — Every Interface All views Control-Plane Data Model  ▶
Solution Architecture v1.0 · Edge Architecture · 2026-09 · 29 views · open source, fully on-premises11-four-data-classes