Heroku API down
status.heroku.com
status.heroku.com
Commenter1: Well they should've never relied on X platform. Single point of failure, etc.
Replyers: It's not Platform X's fault, the engineers should've set up servers like XYZ. It's not like it's hard to do.
Then someone says their app is down, someone else says this sucks, some statistics on uptime get thrown about, and the exact same conversation ensues as the last time any other service went down.
So my honest and sincere question is this: why? Why do "Service X is down" posts get posted and upvoted to the front page? Why do we all have the same discussion each time it happens? It just seems like there's just nothing else to say about it and these sites have status pages where we can all find out for ourselves if they're down or not, so why are we repeating ourselves?
To avoid vendor lock-in, check out OpenShift[1] from Red Hat. It's open source[2] so you can set it up on your own servers if you felt Red Hat weren't providing the service you required, or as redundant servers for fail-over.
[1] https://openshift.redhat.com/community/paas
[2] https://openshift.redhat.com/community/open-source/download-...
Everything worked pretty nice!
And then the 'pay' version created by Activestate and supports PHP and a pretty GUI http://www.activestate.com/stackato
Looks like Red Hat have followed their Linux model where OpenShift Origins is like Fedora, and OpenShift Enterprise is like RHEL. http://www.theregister.co.uk/2012/11/27/redhat_openshift_ent...
I can't think of any direct implications for them with this as it's essentially what Redhat is doing (as you pointed out). Basically the big thing with Cloud Foundry is it fully integrates with Openstack and similar whereas OpenShift is mostly meant for RHEL products.
I'm not a customer of Heroku, I've stuck with Rackspace the last 5 years because they are located in San Antonio and I'm in Austin. However, many project I've worked on the last 12 months use Heroku for production.
They've already built their own complex scaling system that doesn't seem particularly tied to AWS. With a moderate amount of additional work, I don't see why they couldn't deploy it to any provider with an API.
I think we've all misunderstood. They actually aren't reporting service disruptions, but rather their revenue having having "performance issues" with all the SLA crediting they'll have to do.
Not just because of AWS, but on there own they have many issues with platform.. a short list - https://twitter.com/rtdp
we need to seriously shift away of heroku asap !
But status emailing system is really good :)
Don't get me wrong, I wish they would use other AWS regions as well. As a European I really want them to utilize AWS Ireland. But currently there is no need to bitch about how they are handling AWS East outages as there is nothing to handle.
Our game is on Heroku and it's up http://warsocial.com