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
Overcoming Service Communication Issues and Challenges

Once you break things apart into smaller services, you must then put them back together. In other words, individual services...

50 mins
Kube Restaurant

You've been to a restaurant before, right? Have you noticed how everything is structured? Everyone has a job and there...

50 mins
30 Golden Rules of Deep Learning Performance

“Watching paint dry is faster than training my deep learning model.” “If only I had ten more GPUs, I could...

180 mins
Migrating to Microservices

Microservices is one of the latest software architecture styles that promises to deliver benefits such as ease of testing, fast...

50 mins
Fog Computing : Software on the Edge

When the clouds descend to the Earth, we call that fog. When cloud computing moves closer to your end users,...

50 mins
Terraform-ing your Cloud

A large part of embracing DevOps involves embracing automation. Over the last decade we have seen the emergence of “as...