Re:How to build your own CDN with Kubernetes
by MuffinFlavored on Tuesday March 26, 2019 @11:13PM
(#19497906)
> the cloud providers are horrible options
Just to be clear: AWS/DO are horrible options, but Cloudfront is a good option?
Re:How to build your own CDN with Kubernetes
by nrmitchi on Tuesday March 26, 2019 @11:18PM
(#19497920)
I'm not 100% sure what your question is. Cloudfront is already a CDN in itself. You would not use it as a platform for building a new CDN.
I'm not making any claims here about whether or not Cloudfront is better or worse than any other CDN, but can be a perfectly valid choice if you're already within the AWS ecosystem and need a CDN.
Re:How to build your own CDN with Kubernetes
by nerdbaggy on Tuesday March 26, 2019 @11:24PM
(#19497944)
Cloudfront has a lot more POPs then just the ones available for AWS https://aws.amazon.com/cloudfront/features/
Bandwidth and latency are the main concerns or a CDN, and this approach addresses latency, but completely ignores bandwidth. Honestly, a CDN is probably one of the worst possible applications that could be built on AWS (or any other cloud hosting provider) simply due to the extreme bandwidth costs. EC2 egress costs are already an order of magnitude greater than Cloudfront costs, and not even fairly comparable to non-"cloud" options.
Basically, if you want a build a CDN, the cloud providers are horrible options, whether you use Kubernetes or not.
> edited for formatting