It's great for CDN hosting, but honestly too good, which might indeed be tricky for their business models. If IPFS were huge, and you had a large popular static

It's great for CDN hosting, but honestly too good, which might indeed be tricky for their business models. If IPFS were huge, and you had a large popular static site, in theory you don't need a CDN at all, because IPFS is a CDN all by itself. In practice, I think they'd end up moving towards: * seed hosting - distributing content quickly & globally, so that the rest of the IPFS network can immediately access new content, and so that content (old unpopular pages) remains quickly available even if nobody else is looking at it * caching/DDoS protection/etc for non-static content, like most APIs, which IPFS isn't going to be affecting any time soon. This is all a way away of course, none of that matters until IPFS is super popular & widely used, if ever.