3 ms·
Oh wow. This is big! I've been waiting for this for a long time. It's basically Squid in the cloud, but at a scale you couldn't hope to match with your own impl
by mmastrac 16y ago
Oh wow. This is big! I've been waiting for this for a long time. It's basically Squid in the cloud, but at a scale you couldn't hope to match with your own implementation. We used CloudFront+S3 to serve all of the static resources for DotSpots and I was really impressed with it.
Some small downsides (not fatal): I'm assuming that it shares the standard Cloudfront minimum TTL of one hour right now. It also won't pass through query strings to your origin servers. You can invalidate items in your cache, but the API is a bit odd (it's designed more for DMCA violations than updating content).
This might also solve some of the issues when trying to serve gzip-compressed content from Cloudfront. You had to jump through some hoops to get this working with S3: the data in the bucket had to be gzip compressed and you had to serve different content to different browsers depending on whether they supported gzipped content or not. Hopefully it respects the Vary: header.