Amazon CloudFront is a new distributed caching mechanism, designed to get data closer to the user. Amazon says:
It integrates with other Amazon Web Services to give developers and businesses an easy way to distribute content to end users with low latency, high data transfer speeds, and no commitments.
Which is nice and all- but I need to be hearing it from developers. Which is why this caught my eye the other day…
geek footnote: the bigass images on dopplr’s new city pages are served from Amazon’s Cloudfront CDN. And it was really easy.
Needless to say I twittered the comment, and discovered that others in the network are having similar experiences. See davejohnson. Of course these are just two data points, but the fact is my dial is turned very clearly to Matt Biddulph. He is someone I have the greatest respect for, and his technical chops are unimpeachable. I shared an office with Matt and learned years worth of web development technique in months.
Its also very easy using twitter search to come up with further agreement. see @jalegre:
Very happy about Amazon CloudFront, about 100-120 msec for static files like images, js, etc… in Spain (going to France). Faster than S3
Its not rocket science its findability. Meanwhile from a marketing perspective Amazon service naming is impeccable. The company hasn’t put a foot wrong since it started marketing its excess capacity to developers, and naming is very important in framing a market. On Twitter I said:
in other news – cloudfront- what a brilliant product name. descriptive, evocative, right on the money. others could learn from amazon naming