I work for a large CDN. Lots of big customers do this, they shift their traffic around between different CDNs based on a lot of metrics, including price and performance.

I also work for a CDN.

Some of our stuff dynamically utilizes other CDNs. A customer might go try and test deploy something and we might use (AWS or whatever) to do it.

It's CDNs all the way down.

I work for a company people use to build CDNs. Just another turtle. :D

like physical infrastructure or something else? a bit curious (having many neteng friends at many, many CDNs)

I have similar friends!

We the whole stack for most people, but also run our software on "private cdns" for some. We primarily target devs: https://fly.io

Adding my turtle as a CDN employee ;-)

We license software[1] to ISPs/MSPs who then use it to "OEM" Kubernetes clusters to CDN providers.

We should rename our product "Infinite Regress" ;-)

[1] https://gravitational.com/telekube/

I wonder how many of the people in this chain are sitting next to me.....

I've love to see some open source tools that manage this automagically for me. :-)

It would also require an architecture that supports multiple interfaces. Totally doable (the facade pattern comes to mind) but you'd want to calculate the TCO to see it works out financially.

Shameless plug: we have an open source tool you can build stuff like this on. It'll run any logic you can implement in JavaScript, we have people doing things like "send traffic to backend with lowest latency" already, it'd be pretty easy to pull in some API data to pick based on cost.

https://github.com/superfly/fly

Did this a lot with payment processors. Literally had application router settings that could route based on % or switch off once a certain monthly or yearly amount was hit. Configs could be updated in real time.