This weeks outage asks an interesting question regarding hosting providers such as heroku with their "rock-solid ruby platform". I've always taken part of their offering to be that I don't have to think about infrastructure beyond the abstraction that they provide. Perhaps incorrectly I've been under the impression that paying for their service means they will worry about things like redundancy across availability zones or regions leaving me free to just build the app.
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?
I think at least part of the point is that the Law of Leaky Abstractions means you always need to think at least somewhat about the infrastructure, just not as much as they do.
I agree and I imagine AWS, will meet this expectation, eventually. Keep in mind that the Cloud idea is still relatively new. Just look at the history of Amazon's Serivces[1] and you can see that this is the direction that they are going. I think this marks a turning point for EBS. I said this same thing on reddit and was mocked but can you really imagine Amazon letting this happen again?
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.