Strip the marketing from any CDN and four engineering decisions remain: how requests find an edge, how the cache hierarchy is built, how much of the request path you can program, and what the platform lets you observe. Every provider on the market, all thirty-seven we track, is a particular set of answers to those four questions. This is the map for the whole versus series that follows.
Axis one: request routing
Two philosophies dominate. Anycast announces the same IP everywhere and lets BGP deliver the user to the nearest POP: simple clients, instant failover, but routing quality is hostage to internet peering. DNS-based mapping hands out per-query answers from a routing brain: finer control and load awareness, but bound by resolver behavior and TTLs. Akamai built its empire on DNS mapping; Cloudflare and CacheFly bet on anycast; most hyperscaler CDNs blend both. Neither is better in the abstract; they fail differently, and your traffic has an opinion.
Axis two: cache hierarchy
A flat edge cache is only the visible layer. The differences that matter live behind it: regional parent tiers, origin shields, request coalescing that collapses a thundering herd into one origin fetch, and tiered-distribution logic that decides how a 10,000-POP network avoids asking your origin 10,000 times. Networks with many small POPs need deep hierarchies; networks with fewer large POPs, Fastly being the canonical example, keep hierarchy shallow and hit ratios high per site. Long-tail catalogs feel this axis more than any benchmark shows.
Observability, the quiet fourth axis, deserves more procurement weight than it gets: real-time log streaming versus batched delivery, per-request visibility versus sampled analytics, and whether cache decisions can be explained after the fact. When an incident arrives, the network you can interrogate is worth more than the network with the prettier dashboard. Ask every vendor the same question: show me a single misbehaving request, end to end, five minutes after it happened. The demos that follow are more informative than any datasheet in the industry.
Axis three: programmability
The spectrum runs from configuration files applied in minutes, through rules engines, to genuine compute at the edge: Fastly’s VCL and Compute, Cloudflare Workers, CloudFront Functions, Akamai EdgeWorkers, Azion and Gcore functions. The technical question is not whether a platform has edge compute but where it executes in the request path, what latency budget it consumes, what state it can touch and how it deploys. A header rewrite and a stateful auth decision are different products wearing the same keynote slide.
In practice
Score any provider on the four axes against your workload before reading a single benchmark: routing model versus your audience’s network diversity, hierarchy depth versus your catalog’s tail, programmability versus your roadmap, observability versus your debugging reality. The versus articles in this series apply exactly this frame to every pairing on our list, and the assessment applies it to your traffic with measurements attached.
Want the four-axis scorecard run on your traffic across all 37 networks? That is literally what the free assessment is.