Edge Computing
Moving compute towards the user, and what cannot follow it.
5 to work through
-
beginner Multiple choice
A team moves request signing from one region to an edge platform. p50 falls from 140 ms to 35 ms and p99 rises from 220 ms to 900 ms. Error rate is unchanged and the platform reports no throttling. Which mechanism most likely explains the tail?
3 min answer -
advanced
A team proposes moving personalisation to edge functions to cut latency. When does that work and when does it backfire?
2 min answer -
advanced
An e-commerce product page has cacheable content, a personalised recommendation strip, a logged-in header and a live stock indicator. What runs at the edge and where does each piece of state live?
3 min answer -
advanced
Walk me through this one. An executive has read that a delivery network runs more than four thousand points of presence and wants product personalisation moved to the edge this quarter. You have fifteen minutes with them. What do you establish and what do you refuse?
3 min answer -
advanced Multiple choice
Which workloads genuinely belong at the edge, and which become harder there because of state, consistency, debugging or resource limits?
2 min answer
3 terms in this topic
Edge Capability Gradient
The systematic decline in what a location can do as it moves closer to the user - thousands of points of presence with constrained runtimes and no wr…
conceptEdge Computing
Running computation at points of presence near users rather than in a central region, trading capability for round-trip latency.
conceptEdge Function
Code executed at a CDN point of presence close to the user, in a constrained, fast-starting runtime, typically to modify or route a request before it…
Neighbouring topics
Cloud Architecture
General material on designing for cloud platforms.
Compute Models
Instances, containers and functions, and what each is priced and shaped for.
Cloud Storage
Object, block and file storage, and the access patterns each suits.
Cloud Databases
Managed relational, key-value, document and analytical services.
Containers
Images, registries, immutability and the deployment model they enable.
Kubernetes
The reconciliation loop, and whether the workload needs what it provides.
Serverless
Scale to zero, per-request billing, cold starts and connection limits.
Autoscaling
Signals, delays and bounds — and the maximum that caps a runaway bill.
Load Balancing
Distributing traffic, health checking, and removing failures from rotation.
Multi-Region Architecture
Surviving a region, and the data consistency price of doing so.
Availability Zones
The unit of correlated physical failure, and what zones do not protect against.
Disaster Recovery
Backup-restore, pilot light, warm standby and active-active postures.
Backup Strategies
Scope, immutability, separation, and the restore drill that makes it real.
Infrastructure as Code
Declarative infrastructure, drift, state files and rebuild-from-empty.
Landing Zones
A governed foundation of accounts, network, identity and guardrails.
Managed Services
Which operational responsibilities actually transfer, and which do not.
Cloud Migration
Per-application disposition, sequencing and the capability change underneath.
Multi-Cloud
Best-of-breed, portfolio and portable — three very different costs.
Cloud Governance
Preventive policy, tagging, quotas and cost and security guardrails.