Writing

Architecture explainers. Plate 6 of 6.

How CDNs Decide Where to Serve a Request ArchitectureHow CDNs choose an edge: Anycast and GeoDNS request routing, health-aware failover, cache hierarchy, and failure domains — grounded in public docs.2026-09-1818 minAkamai CDN Architecture: DNS, Tiered Caching, and SureRouteA source-grounded Akamai CDN architecture teardown separating Edge DNS, GTM steering, Tiered Distribution, and SureRoute origin paths.2026-09-148 minHow Fastly's Edge Network Handles HTTP Traffic: Fastly Architecture: Routing and ExecutingHow Fastly handles HTTP at the edge: Anycast routing, Varnish cache, WASM compute, request path, and failure domains — grounded in public docs.2026-09-1415 minHow Google Global Load Balancing Works: Google Global Load Balancing: Edge Routing and PlaHow Google Global Load Balancing steers HTTP traffic with Anycast, health checks, and backends — failure domains and request path grounded in public docs.2026-09-1419 minHow AWS CloudFront Distributes Content GloballyHow CloudFront distributes content globally: DNS to network-nearest edges, cache/origin path, Functions and Lambda@Edge, failure domains — grounded in public AWS docs.2026-09-1410 minHow Cloudflare Routes Traffic Across Its Global Edge NetworkHow Cloudflare routes traffic at the global edge: Anycast BGP to a network-nearest PoP, Magic Transit packet path, DDoS mitigation layers, and failure domains — grounded in public docs.2026-09-1411 min

No posts match that search.