A Look at Atlassian's April 2022 Jira Outage
May 4, 2022What lessons can you take from this incident for your own organization?
It’s been the talk of the town for the last few weeks: Atlassian suffered a 2-week outage for a small percentage of its customers. Last week they published their Post-Incident Review on the topic. And today, I want to respond to it.
The review begins with a short letter from Atlassian co-CEOs Mike Cannon-Brookes and Scott Farquhar, in which they explain that “one of our core values is ‘Open company, no bullshit’.” Then they go on to explain why Atlassian is so reliable and trust-worthy, practically ignoring the incident that had just occurred.
I’m reminded of a news story on my local TV station many years ago. There had been a shooting at a convenience store, across the street from a police station. The news reporter was interviewing a police officer and asked “Should citizens be worried for their safety here?” and his reply was “No, of course not. It’s very safe. There’s a police statoin across the street.” 🤦
I’ve also written up a longer look at the review, praising the good, and criticizing the bad.
What's the ideal ratio of devs to QAs?
Of course, as a consultant, I can confidently tell you: It depends!
Short-term alternatives to code freezes
Use a code freeze as a reminder that there are still quirks to be worked out, and make an effort to work them out.
Adventures in DevOps 114: Progressions Through Programming Languages
What are the types of program languages required in DevOps? What are the pros and cons of each?