Posted by Charles
As an SRE (Service Reliability Engineer) at Heroku, one of the things I’m exposed to is how much work happens behind the scenes in order to create what we call “non-events” for you, our users. A non-event is turning something that would typically create work for an application hosted on traditional infrastructure into something that the user won’t even notice. This is something we put a lot of energy into because we believe in letting our users run apps instead of managing infrastructure. We make this investment because we know that for every hour you spend managing infrastructure, that’s an hour less spent on building or maintaining your application. We know that you need to be able to iterate quickly in order to have a competitive advantage and you’ll have a more difficult time doing that if you’re also managing infrastructure.
Two examples of these non-events from recent weeks are the “Shellshock” security flaw and Amazon having to reboot a large number of instances due to a security vulnerability in their hypervisor. This post is about what happened behind the scenes at Heroku to shield our users.Read more →