Edge Computing Explained: Where Compute Actually Sits
Edge is a location, not a product. We map where compute physically sits in real deployments — device, far edge, regional edge, cloud — and what that means for latency, bandwidth, and failure behavior. Then we separate the workloads that genuinely need the edge from those that are cheaper in the cloud. We cover the mechanics: how a request gets routed to the nearest edge node, how state is handled when the edge is stateless by design, and how to manage fleets of heterogeneous nodes. The core question is practical: what does your workload actually require, and which tier can meet it?
Topics covered:
- The compute tiers: device to far edge to cloud
- Latency and bandwidth budgets per tier
- Routing to the nearest node and state placement
- Which workloads actually benefit from the edge
Related articles
Multi-Region Deployments and Latency
Speed-of-light RTT floors, active-passive versus active-active architectures, DNS-based routing, and replication lag — the real tradeoffs of running in multiple regions.
Autoscaling Is a Latency Decision
Reaction time versus provisioning time, HPA sync intervals, cooldowns, and hysteresis — why autoscaling is a latency engineering problem before it is a capacity problem.
Containers Aren't Lightweight VMs
Namespaces, cgroups, seccomp, and the real isolation boundaries — what containers actually isolate and what they don't.
More in Cloud & Infrastructure
Container Orchestration Basics: API Server, Controllers, and Scheduler
Container orchestration from first principles — what the API server, controller manager, and scheduler actually do, with Kubernetes as the working example.
DetailsThe Cost of Distributed Systems: Coordination, Consistency, and Failure
What distributed systems actually cost — coordination, consistency, and failure taxes — quantified with quorum math, tail latency, and retry-storm dynamics.
DetailsDNS and Traffic Routing in the Cloud: From Resolver to Anycast
How DNS actually routes traffic in the cloud — record resolution, CDN anycast, geo routing, load balancer handoffs, and how TTLs shape your failover story.
DetailsMulti-Region Architecture: Active-Active, Failover, and Replication
The real mechanics of multi-region deployments — where writes land, how replication propagates, what failover flips, and the latency math that constrains every design.
DetailsObject Storage Under the Hood: PUT, GET, and Erasure Coding
What happens inside an object store — the PUT and GET paths, metadata partitions, erasure coding, and why object storage is eventually consistent.
DetailsAutoscaling Explained: The Controller Loop Behind Horizontal Scaling
How autoscaling actually works — the metrics window, desired-replica calculation, stabilization, and why naive CPU-based scaling oscillates under real load.
DetailsServerless Cold Starts, Measured: Where the Latency Actually Goes
Measured cold-start latency across Lambda, Cloud Functions, and container runtimes — what actually takes time and which optimizations genuinely reduce it.
DetailsKubernetes Scheduling Visualized: The Filter-Score Pipeline
What the Kubernetes scheduler actually does — how pending Pods become assigned to Nodes, the filter-then-score pipeline, and how taints and affinity shape placement.
DetailsContainer Images Explained: Layers, Manifests, and Digests
How container images are actually built and run — layers, manifests, content digests, and what the runtime does at pull and run time.
DetailsDepth, delivered weekly
One technical dispatch a week — articles and episode notes before they go public.
One technical dispatch per week. No noise.