An Excerpt from “Networks at the Edge: Designing Low-Latency, High-Throughput Systems”

An Excerpt from “Networks at the Edge: Designing Low-Latency, High-Throughput Systems”

The following is an excerpt from “Networks at the Edge: Designing Low-Latency, High-Throughput Systems” by Thomas Foster, available on MixCache.com.

Introduction

The distance between a user’s intent and your system’s response is measured in milliseconds—and those milliseconds determine whether a movie starts smoothly, a game feels fair, or a sensor network keeps up with reality. As bandwidth grows and compute becomes abundant, latency and variance have become the real constraints. This book is about designing networks and systems that meet those constraints by moving data, compute, and decision-making as close to the user as possible, while sustaining high throughput and keeping costs and operational risk under control.

Edge computing and modern content delivery networks (CDNs) are no longer specialized add‑ons; they are the default substrate for interactive services. Whether you are shipping a new real‑time collaboration tool, a live streaming platform, a multiplayer game, or an IoT control plane, you are building on a path that traverses last‑mile networks, peering fabrics, and a federated edge. The challenge is to shape this path—through placement, routing, caching, and protocol choices—so that your tail latencies shrink, your jitter becomes predictable, and your throughput remains high even under stress.

This book takes a practitioner’s view. We focus on concrete trade‑offs: when to add a new point of presence versus optimizing peering; how to size caches and choose eviction policies; which load‑balancing strategy to prefer as concurrency scales; and how to tune congestion control without harming fairness or stability. For teams building streaming, gaming, and IoT platforms, we emphasize the end‑to‑end experience: from first byte to steady state, from P50 to P99.99, across devices, networks, and geographies. The goal is to help you balance performance with cost and reliability—and to do so with a toolkit you can adapt to your constraints.

At the protocol layer, the landscape is shifting fast. QUIC and HTTP/3 change transport dynamics; modern congestion control like BBR redefines bandwidth and latency sharing; and real‑time channels via WebSockets and WebRTC bring conversational timing to the web. These innovations can unlock dramatic gains, but only when paired with sound engineering: queue management and backpressure, circuit breaking and load shedding, and careful observability that exposes the long tail, not just the median.

Operations are as critical as architecture. Edge systems fail in partial, regional, and path‑specific ways. Brownouts, misrouted traffic, cache stampedes, and asymmetric congestion are routine. We will discuss how to detect, isolate, and respond to these events using tracing, metrics, and active measurements; how to design graceful degradation paths that preserve core value under duress; and how to run load, soak, and chaos experiments that build confidence before launch day. Security—TLS and mTLS at scale, DDoS and bot mitigation, and zero‑trust patterns—must be designed in, not bolted on.

Finally, this book is organized to be used. Early chapters develop principles and a shared vocabulary for latency‑sensitive design. Middle chapters dive into the mechanics of placement, routing, caching, load balancing, congestion control, and real‑time delivery. Later chapters focus on observability, reliability, operations, and governance, culminating in case studies drawn from streaming, gaming, and IoT deployments. Each chapter highlights practical patterns, common failure modes, and decision frameworks that you can take back to your architecture reviews.

Latency and throughput are not merely properties of your servers—they are properties of the path, the protocols, and the operations that bind them. By the end of this book, you will be equipped to shape that path: to place capacity where it matters, route requests intelligently, cache what you can and compute what you must, and continuously measure and improve the experience. The edge is not a place on a map; it is a discipline. Let’s get to work.

Read “Networks at the Edge: Designing Low-Latency, High-Throughput Systems” on MixCache.com →