At one level throughout Tsinovoi’s tenure at Akamai, the choice was made to freeze all community growth for a full yr after Akamai skilled a number of outages in a single quarter. The engineering crew had capability to innovate, however the danger of any change outweighed potential advantages, he recalled.
Cloudflare has additionally suffered its share of latest outages together with a firewall incident in December. The sample is constant: CDN suppliers that bundle infrastructure with quickly evolving utility companies create fragility within the foundational layer that should stay steady. Tsinovoi mentioned that he has had every day buyer conversations about redundancy necessities since Cloudflare’s December outage.
“We should go and have a redundancy edge. We can not proceed to depend on a single vendor anymore,” he mentioned, characterizing the present buyer sentiment.
How IO River’s multi-edge platform works
IO River doesn’t have its personal CDN or edge infrastructure. Fairly, the platform creates a digital layer that sits above heterogeneous CDN infrastructure as a kind of overlay.
The structure addresses a basic compatibility drawback: Edge platforms from Akamai, Cloudflare and Fastly all use totally different underlying runtime environments. Code written for Fastly gained’t essentially execute on Cloudflare with out modification.
The IO River platform leverages WebAssembly and JavaScript because the execution layer on edge networks. Clients write microservices as soon as in JavaScript or WebAssembly. IO River’s virtualization layer handles the runtime atmosphere variations and distributes that code throughout a number of edge platforms.
