We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
DevOps Patterns and Antipatterns for Continuous Software Updates | Baruch Sadogursky
Learn the patterns and antipatterns of continuous software updates and discover how to adopt a culture of rapid innovation, minimizing downtime and maximizing trust with key speakers discussing DevOps strategies and real-life examples.
- Two main reasons to update software: new features and security
- Most companies do not release new features fast enough, causing customers to seek alternatives
- Trust is a major issue when updating software, as users don’t always want to update immediately
- Canaries and progressive delivery can help reduce risks and increase trust
- Updating software is not just about deploying new features, but also fixing bugs and security vulnerabilities
- Companies should transition from bulk and rare updates to tiny and frequent updates
- The key to successful updates is to observe what’s going on and be able to rollback if something goes wrong
- DevOps is not just about Agile and Scrum, but also about observability, monitoring, and rollback
- Java 8 update frequency is an example of what not to do, as it took years to update
- Boeing 777 software problem was solved by putting all software engineers on board
- Google Wi-Fi router demonstrates the importance of self-updating software
- Cloudflare’s new rules are deployed to battle bad guys and update software quickly
- IT industries take a long time to adopt new updates due to lack of trust and fear of failure
- The old saying “you broke it, you fix it” is not applicable in software update scenarios
- Trend of continuous updates is gaining popularity due to speed and frequency
- 2012 investment firm example shows the importance of observing and rollback
- MoviePass example shows the importance of continuous updates and minimizing downtime
- DevOps Research and Assessment Institute report highlights the importance of continuous updates
- Most companies do not adopt Agile and Scrum due to lack of trust and fear of failure
- Toyota’s Luban concept and Danish Football Association’s IT strategy are examples of successful continuous updates
- Always protest on hidden service first, like Canary releases and progressive delivery
- Some companies have transitioned to extremely tiny and frequent software updates, like the elite cohort
- One of the most important documents in our industry is the state of DevOps report