starts in 10 seconds
DevOps Patterns and Antipatterns for Continuous Software Updates

DevOps Patterns and Antipatterns for Continuous Software Updates

31m

So, you want to update the software for your user, be it the nodes in your K8s cluster, a browser on user’s desktop, an app in user’s smartphone or even a user’s car. What can possibly go wrong?

In this talk, we’ll analyze real-world software update fails and how multiple DevOps patterns, that fit a variety of scenarios, could have saved the developers. Manually making sure that everything works before sending an update and expecting the user to do acceptance tests before they update is most definitely not on the list of such patterns.

Join us for some awesome and scary continuous update horror stories and some obvious (and some not so obvious) proven ideas for improvement and best practices you can start following tomorrow.

Share some ❤
Date: October 10, 2019
Play
My List

Leave Review

Your email address will not be published. Required fields are marked *

ARE YOU IN?

Get enhanced value from the site through the exclusive “members-only” content. 200,000+ subscribers already enjoy our premium stuff.