When to use Amazon Cloudfront or S3 -


are there use cases lend better amazon cloudfront on s3 or other way around? i'm trying understand difference between 2 through examples.

amazon s3 designed large-capacity, low-cost file storage in 1 specific geographical region.* storage , bandwidth costs quite low.

amazon cloudfront content delivery network (cdn) proxies , caches web data @ edge locations close users possible.

when end users request object using domain name, automatically routed nearest edge location high performance delivery of content. (amazon)

the data served cloudfront may or may not come s3. since more optimized delivery speed, bandwidth costs little more.

if user base localized, won't see difference working s3 or cloudfront (but have choose right location s3 bucket: us, eu, apac). if user base spread globally , speed important, cloudfront may better option.

both s3 , cloudfront allow domain aliases, cloudfront allows multiple aliases d1.mystatics.com, d2.mystatics.com , d3.mystatics.com point same location increasing capacity parallel downloads (this used recommended google introduction of spdy , http/2 of lesser importance).

cloudfront also supports cors of 2014 (thanks sergiopantoja).

* note: s3 can automatically replicate additional regions of 2015.


Comments

Popular posts from this blog

c++ - How do I get a multi line tooltip in MFC -

asp.net - In javascript how to find the height and width -

c# - DataTable to EnumerableRowCollection -