DevOps Patterns and Antipatterns for Continuous Software Updates
So, you want to update the software for your user, be it the nodes in your K8s cluster, a browser on the user's desktop, an app in the user's smartphone, or even a user's car. What can possibly go wrong?
In this talk, we'll analyze real-world software update failures and how multiple DevOps patterns that fit various scenarios could have saved the developers. Manually ensuring 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.
Kat Cosgrove (https://twitter.com/Dixie3Flatline) - Developer Advocate at JFrog
Kat Cosgrove is a Developer Advocate at JFrog, and an actual cyborg. Her professional background has run the gamut from bartender, to video store clerk, to teacher, to software developer. She credits this wide-ranging experience for her success as a speaker, developer, and advocate. Her specialty is approachable 101-level content for junior developers or anyone else who considers themselves a newbie, with a particular focus on DevOps.
When she's not building demos or at a conference, she spends her time playing video games, watching horror movies, and reading science fiction. She lives in Seattle with her cat, Espresso, who is the real brains behind the operation and actually ghostwriting all of her tweets.
