DevOps Patterns and Antipatterns for Continuous Software Updates


Duration: 15 mins
Baruch Sadogursky
Head of Developer Relations - JFrog, Inc.

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 keynote, 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.

You may also be interested in

50 mins
Level-up Your DevOps with GitHub Actions and Kubernetes

Are you looking to rapidly deploy your content? Are Docker containers in your future? Come for this demo-only presentation where...

50 mins
Monitoring Multiple Cloud Providers Made Easy

Most organizations have two or more cloud providers in order to spread risk. Monitoring deployments across these cloud providers however,...

50 mins
Communication Patterns in Microservices

Teams adopt microservices understanding the structure of the architecture but with a poor understanding of how to get all the...

180 mins
Deconstructing a Monolith

Starting with an existing monolithic e-commerce application, you will learn how to effectively apply and use different tools and projects...

50 mins
Flying through Cloud Native (CNCF)

The maturing of industry projects and tools around cloud development and administration has led to the formation of the Cloud...

25 mins
SRE or Devops - I am an Architect - Why Do I Care?

The most important thing about applications developed for the cloud - is keeping them running. More important than even writing...