That only took 21 months since I asked them nicely. What I don’t like about what I’ve read so far is that they are not using a lazy-loading proxy (ala Akamai, EdgeCast, Panther) and are instead opting for S3 as the content origin. That sucks, because it basically means that you have to do something in order to get your content onto their network. With a lazy-loading proxy, you just tell your CDN provider to effectively make static.whatever.com a mirror of www.whatever.com. It’s much simpler.

I think this is the fifth blog post that I’ve written today.  Seriously.  Just a quick pointer to an article on Xconomy that I wrote this morning about Amazon’s new Elastic Block service.

if you feel compelled to comment, please try to think of something interesting to say. youtube needs remarks like “awesome song” and “this video sucks” like it needs another shaky, blurry, garbled & distorted, 27-second camera-phone clip of Feist performing 1234 in [YOUR TOWN HERE]. thank you.

I was walking through the electronic turnstile onto the T the other day and noticed a partially obscured Microsoft Visual C++ runtime error dialog box on the screen!

I put some thoughts and scrappy data about memcached over on the StyleFeeder tech blog.

Ben Adida is a super nice guy until you start misusing message digests. He once gave me a smackdown (I like to think of it as a learning experience) that was very helpful and now he’s done the same thing in public: don’t Hash Secrets.

Don’t make the cryptographers cry. Especially not Ben.

How to scale « François Schiettecatte’s Blog
It not about the language, it is about the architecture.

Nearly: good algorithms and proper caching are also part of the picture.  Sure, caching is part of good architecture, but it makes such a difference that it’s worth calling it out separately.

(This should really be a much longer post…)