Edge Data Consistency
Replicated read state at hundreds of locations, and writes that still go to one.
4 to work through
-
advanced
A mobility platform wants to place data close to users in many regions. Which data can be replicated and which cannot?
2 min answer -
advanced
A social platform serves user profiles from edge caches worldwide. A user updates their profile and still sees the old one. How should this be handled?
1 min answer -
advanced
After a price change you issue a CDN purge and every point of presence returns 200. Twenty minutes later customers in one region still see the old price, and a hard refresh fixes it for some of them. Where do you look and in what order?
2 min answer -
advanced
You enforce a rate limit of 100 requests per minute per user at the edge, across 40 locations. Abuse monitoring shows a user making 3,000. Explain.
2 min answer
3 terms in this topic
Edge Data Consistency
The consistency model available when data is replicated to many edge locations, where strong consistency would eliminate the latency benefit that mot…
patternRead Local Write Global
Replicating read-only state to every edge location while directing writes to a single authoritative region, which is the arrangement most edge data s…
patternVariant-Aware Purge
Invalidating every cached representation of a resource rather than one URL - because content negotiation and query parameters create many objects und…
Neighbouring topics
Edge, Mobile & IoT
General material on architecture beyond the data centre boundary.
Mobile App Architecture
Layering, navigation, background execution, and the platform rules you do not set.
Offline-First
Treating connectivity as an optimisation, with a local store as the source of truth.
Sync & Conflict Resolution
Two devices that both changed the same record while neither could see the other.
CRDTs
Data types that converge without coordination, and the semantics you must accept.
Mobile Release Strategy
Store review, staged rollout, and supporting versions you can never force off.
Push & Background Work
Delivery that is best-effort, and an operating system that will kill your process.
Device Identity
Identifying a thing rather than a person, and rotating a credential you cannot type.
Edge Compute Topologies
Regional, metro, on-premises and on-device, and what each tier is genuinely for.
Edge Functions
Short-lived compute at the CDN, its runtime limits, and what must stay at origin.
IoT Ingest Architecture
Millions of small, unreliable, frequently duplicated messages arriving continuously.
Device Provisioning
Getting identity and configuration onto hardware at manufacture or first boot.
Fleet Management
Inventory, health, configuration and grouping across devices you will never see.
OTA Updates
Updating firmware over a flaky link, with rollback, and without bricking the device.
Constrained Protocols
MQTT, CoAP and their kin, chosen for power, packet size and intermittent links.
Device Telemetry at Scale
Deciding what a device sends, how often, and what is aggregated before it leaves.
Digital Twin
A server-side model of a physical thing's reported and desired state.
Edge Security & Attestation
Secure boot, hardware roots of trust, and proving what is running on a device.
Physical-World Failure Modes
Power loss, tampering, clock drift, thermal limits, and a truck through the fibre.