Now why would we need to worry about the same things everyone else does that isn't in the cloud? That's right: the cloud doesn't solve these problems. It's not a shining moment. It's just the fact that in these cases you'd have to be an idiot to think the cloud somehow elevates you from this problem.
Now what cloud does give you can be valuable, though sometimes marginal in comparison to problems like having cascading failures outside your control because everyone happens to be sharing the same network or so on. I'm not knocking the cloud as much as I'm knocking people who pretend it's actually elevating computing away from traditional concerns.
I'm a huge fan of heroku so I'm really just trying to clarify, are these services offering to take care of my infrastructure requirements or do I need to think about adding redundancy/failover etc. myself?
edit: http://www.heroku.com/how/architecture#routing-mesh is what set my expectations.
Decouple using SQS, SNS. Use ELB to split traffic across regions. Rely on S3 and SimpleDB for robust storage.
I am curious about how much of Amazon's internal systems rely on EBS.
I suspect Amazon dont use EBS much, avoiding a point of failure, and it is a newer service.