---

There is no denial that the Crowdstrike outage caused significant impacts, including some very critical and unacceptable losses. These should have been prevented. It made everyone in IT think about how such an issue could have slipped through every stage before hitting production. Couldn’t they have used various proven product deployment techniques? I’ll leave that thought there, as many are already discussing it.

However, I see the outage as beneficial in some ways. Let’s count the positives:

1. I bet Crowdstrike has taken this very seriously and will bring better controls to avoid any future and bigger losses.
2. It’s a wake-up call (though a costly one) for their competitors and the entire ecosystem to build preventive and backup measures.
3. Untapped opportunities in edge computing have been unveiled.

Some lighter observations include:

1. The stock price is down by 11%. If you were waiting for an entry, this is the right time. Remember, the product has been delivering its purpose all this while. This is a process failure, not the product’s.
2. You had a paid day off! 🤣

If you’re an IT professional, you should know the various product deployment techniques. Make sure to check out this link for a quick learning session: Deployment Strategy for Engineering Leaders.

I was brainstorming with some friends about rollback strategies that can be considered for scenarios like these. Some interesting ideas came up, which I might discuss in the next blog. Meanwhile, if you have any suggestions or thoughts, feel free to comment or reach out to me. Let’s discuss over a call! 😊

Visit: www.krkaleraj.com

#crowdstrike #crowdstrikeoutage #windowsbluegreen #softwareengineering #releasemanagement #engineeringleaders