I'm not saying you don't have a point, but imo your comparison of Heroku's 76 vs. Tumblr's 42 is not apples-to-apples. I think you have to at least put an asterisk by the 76. What OP is complaining about is a early-Twitter-days-like unreliability over a long interval, not a one-time outage that has a single explanation and for which Heroku took completely responsibility.
For my part, at the moment at least, I still have more confidence in Heroku than Tumblr, 76 vs 42 notwithstanding.
- I wanted to use Sinatra to 301 old tumblr urls
- Call me weird but I loathe seeing *.html in urls and that's the only thing you can do with S3 root object (when I checked a few months ago)
- something I can't remember. maybe it was cf edge server time to update when altering updates.
You can configure name of index file, and that will be displayed for requests against root URL and subdirectories (such as blog posts) as well. No need for having .html in URLs.
The only problem I've encountered with S3 web hosting is that it does not let you host naked domains.
OK that was actually the answer.
Honestly there's a little bit of "because I did it myself and I'm awesome it won't fail." That's hubris and very typical of young engineers.
Letting someone else manage it for you is probably the right thing for a startup to do. You just need to choose someone with a good, proven uptime record. That is what should guide your decision.. with so many things in engineering.
My point is if uptime is your goal you should go with a proven solution. Relying on an unproven custom setup to be 100% mistake free smacks a bit of young engineer hubris.
In 2011, Tumblr was down for 42 hours.
In 2011, Heroku was down for 76 hours in one incident alone.
And that's all before you get to the hubris of the assumption that your custom coded setup will perform better. A more sensible argument would be to move to a host with a better proven uptime record, such as Blogger (nearly 100%).
Sources: http://allthingsd.com/20111215/tumblr-had-42-hours-of-downti... https://status.heroku.com/incident/151