Edge Compute Topologies
Regional, metro, on-premises and on-device, and what each tier is genuinely for.
4 to work through
-
intermediate
A content platform must decide what runs at the edge, in a region, and centrally. How should the topology be reasoned about?
2 min answer -
intermediate Multiple choice
A ride-hailing platform in the mould of Grab operates in eight cities across four countries. Matching a rider to a driver needs the live positions of nearby drivers and must answer in under 500 ms. Payments, identity and analytics are central. Where should the matching engine run?
2 min answer -
advanced Multiple choice
A content and application platform must choose between many small points of presence and fewer larger regional sites. What trades off?
1 min answer -
advanced
A team proposes moving an API to edge functions to reduce latency for international users. What do you check before agreeing?
2 min answer
2 terms in this topic
Compute Tier Placement
Deciding which of on-device, on-premises, metro, regional or central compute a workload belongs to, from its latency, data volume and autonomy requir…
conceptEdge Compute Topology
The choice of where computation sits along the path from device to region, trading latency and autonomy against manageability and consistency.
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 Functions
Short-lived compute at the CDN, its runtime limits, and what must stay at origin.
Edge Data Consistency
Replicated read state at hundreds of locations, and writes that still go to one.
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.