From configuration authority to edge runtime state
IXCDN uses deterministic snapshots and checksum notifications so edge and DNS nodes can update without a database dependency on the hot path.
IXCDN treats the database as the source of configuration truth. The control plane reads sites, certificates, WAF policies, DNS records and Geo address data, then compiles them into snapshots that are optimized for data planes.
After a snapshot changes, the control plane publishes gossip checksums so edge and DNS nodes can discover the update. Nodes then pull the latest blob from internal endpoints and atomically swap their in-memory runtime state.
This keeps the database out of the traffic hot path. Even if the configuration store is briefly unavailable, data planes that already loaded their state can continue serving production traffic.