Leveraging S3 as a CDN in a modern web application build

#1

Post by dslama » Tue, Sep 05, 2017, 2:48 PM UTC

Leveraging S3 as a CDN in a modern web application build
medium.com

Re: Leveraging S3 as a CDN in a modern web application build

#2

Post by d883kd8 » Tue, Sep 05, 2017, 2:58 PM UTC

We're just using "web-scale" unironically now to describe things meant to operate on the scale of the world wide web. I guess this is progress?

Re: Leveraging S3 as a CDN in a modern web application build

#3

Post by jgrahamc » Tue, Sep 05, 2017, 3:06 PM UTC

This is a very confusing article. It begins:

    Web applications typically begin their life serving their
    own static assets(javascript, css, etc) to the browser. An
    alternative to this strategy would have these assets be
    hosted by a highly-available content delivery network or 
    CDN (e.g. Amazon Simple Storage Service (S3)).

S3 isn't a CDN. It's a storage service. And it has egress charges (per request and bandwidth). Using it as a CDN seems like madness. Especially when Amazon has a CDN called CloudFront. Or you could stick everything in S3 and use a third party, free CDN like Cloudflare. By all means store your assets in something like S3 but don't use it as a CDN. It's not.

Re: Leveraging S3 as a CDN in a modern web application build

#4

Post by dslama » Thu, Sep 07, 2017, 2:03 AM UTC

jgrahamc wrote: post #3

This is a very confusing article. It begins: Web applications typically begin their life serving their own static assets(javascript, css, etc) to the browser. An alternative to this strategy would have these assets be hosted by a highly-available content delivery network or CDN (e.g. Amazon Simple Storage Service (S3)). S3 isn't a CDN. It's a storage service. And it has egress charges (per request and bandwidth). Usi…

Yeah, you right! Thanks, I've updated the post