caching - cloudfront cache hits only pricing -


lets using aws's s3 connected cloudfront .

and s3 sends 1 image file of size 1 mb cached on cloudfront's edge nodes.

then cached image file downloaded 1 million times cloudfront's edges .(the image not grabbed again s3 ).

do pay

1-the bandwidth transferring file s3 cloudfront edges.

2- bandwidth transferring file s3 cloudfront edges + bandwidth 1 million downloads cloudfront edges .

also , if answer 2 , means caching doesn't save money @ ? impove performance ?

and if that's case why use cloudfront instead of cloudflare since cloudflare provides free bandwidth ? (is there catch there ?)

you don't pay s3 cloudfront:

if using aws origin, effective december 1, 2014, data transferred origin edge locations (amazon cloudfront "origin fetches") free of charge.

you pay outbound transfer. if stay lowest-priced cloudfront tier, you'll pay $85 data plus 75 cents http requests.

in comparison, using s3, ignoring free transfer tier, you'll pay $90 data plus 40 cents http requests.

so, why use cloudfront? first, users lower latency download 1mb file. second, price remains lower go bandwidth tiers- if shipping 300tb of data per month, final tier 20% cheaper s3 price.

there places offer better bandwidth pricing aws, in server/file/cache variations. if use cloudflare you'll pay s3 cloudflare. may need pay once (1mb), in reality it'll more once.


Comments

Popular posts from this blog

Email notification in google apps script -

c++ - Difference between pre and post decrement in recursive function argument -

javascript - IE11 incompatibility with jQuery's 'readonly'? -