I was skeptical of the new pricing plan at first, but then I realized it was introducing more accurate price signals to users. This helped a lot of people realize that their apps were doing really stupid things. I argue this here:

https://plus.google.com/116396240707733722472/posts/EHpaKDWM...

Sadly no mention of multipart upload. If you use S3's multipart upload feature you can get similar performance for one file by uploading multiple parts of the file at once. I saw a substantial throughput improvement when I implemented some multipart upload code, even when uploading from EC2.

Totally true. However, I had to limit the scope of this post somewhere, and in this case, I focused on multithreaded upload of smaller objects, as mentioned in the first paragraph. We do have some larger object uploads, though they are a minority. I may do a separate followup post on high performance single file uploads through multipart uploading.

I'm surprised content aware image resizing didn't make the list. It is a few years old but still pretty neat:

http://www.youtube.com/watch?v=qadw0BRKeMk

That deserves an update, yes.

That reminds me of this page in which the author created a large binary tree of pages and watched how various crawlers walked the tree.

http://www.drunkmenworkhere.org/219

Not all, if you look at the south part of the drawing there is still an above ground parking structure :(

Isn't that Chrome OS? Just enough OS to get your employees on to the websites that they use to do their job. (Only applicable for certain types of jobs, though)

While much of vender software has migrated to the web, purpose-built IT is still heavily reliant in old applications that date back decades.

Even something as simple as a time management system may take several years and tons of money to transition from decade-old WinForms app to new web app.

But many of the backend services powering Kindle are based in Seattle.

Uhh, did you even read it? Under "Impact to Multiple Availability Zones", last paragraph:

"There are three things we will do to prevent a single Availability Zone from impacting the EBS control plane across multiple Availability Zones. The first is that we will immediately improve our timeout logic to prevent thread exhaustion when a single Availability Zone cluster is taking too long to process requests. … To address the cause of the second API impact, we will also add the ability for our EBS control plane to be more Availability Zone aware and shed load intelligently when it is over capacity. … Additionally, we also see an opportunity to push more of our EBS control plane into per-EBS cluster services. By moving more functionality out of the EBS control plane and creating per-EBS cluster deployments of these services (which run in the same Availability Zone as the EBS cluster they are supporting), we can provide even better Availability Zone isolation for the EBS control plane"

It is hard to test emergent behavior in large distributed systems, you pretty much have to actually run the tests live to see what is going to happen and see if it aligns with your predictions.

I don't think it covers authentication, but take a look at Thrift:

http://incubator.apache.org/thrift/

It provides an RPC framework and IDL.

If only thrift had some sort of signal/event support :(.