Have you ever seen a tweet like this and wondered what it was? It’s #HugOps! We’re sending you some giant #HugOps today (and every day), and hope that after reading this you feel inspired to pass on some #HugOps, too.
If you’re hosting on AWS, you can expect some pretty excellent reliability and availability. If your service isn’t responding, it’s likely an issue with your own code. On the other hand, system outages do happen. They’re usually pretty minor. Sometimes they're not.
Letting the right people know about incidents is an easier-said-than-done kind of task. Every incident is different and some notifications simply don’t need to land in everyone’s inbox. We’ve listened to a lot of customers who like the idea of posting an incident to their status page, but not having that incident sent as notifications to all their subscribers.
I’ve seen my share of terrible status updates. As Founder and CEO of a SaaS platform for database performance management, VividCortex, I know the power of a great status update to build or destroy trust. Unfortunately, I see more bad status updates than good ones.
Nothing fills out the “worst-case scenario” column quite like a data breach. For the countless teams out there who work hard to protect their customers’ data, the idea of compromising that trust is a nightmare. Data breaches are on a lot of minds lately with the 2017 Equifax data breach, which exposed personal data from 143 million American consumers. The company, security industry, and regulators have a huge task of working out the details on how something like this happens.
