Architecture

Synopsis This chapter describes the main architecture patterns for multi-CDN and how to choose between them. It explains DNS-based steering, layer 7 proxy or aggregator designs, client-side selection, and hybrid approaches. It focuses on behavior, failure modes, latency impact, and operational complexity. DNS-based steering Authoritative DNS answers with records that point to different CDNs based on geography, network, or other criteria. This pattern has low per-request overhead because the routing decision happens before HTTP, but it reacts on the scale of DNS caching. Time to live and resolver behavior affect how quickly changes take effect. Geo and ASN databases must be maintained. Health-driven routing requires either short TTLs or resolver-aware mechanisms that may not be consistent across networks. DNS steering is simple to deploy and scales well, but it is limited in how fast it can respond to sudden failures and it has coarse visibility into per-request signals. ...

Synopsis This chapter defines multi-CDN and explains when the approach improves service outcomes. It describes benefits in availability, performance, and vendor risk, and it outlines added complexity in operations, security, and cost. A simple decision framework and a migration overview provide a practical start point. Definition Multi-CDN is the practice of serving the same property through more than one content delivery network under a single control plane. Requests are routed to one of several providers based on policy. Policies consider jurisdiction, health, performance, and cost in that order of precedence. Correctness and user experience remain the primary constraints. ...