Our meetup group is a community platform for everyone interested in DevOps. No matter if you are a front-end designer, backend developer, tester, team lead or system administrator – if you’re passionate about the DevOps movement you are welcome! We want to share experiences, new information and learnings. Our focus will be on DevOps topics ranging from implementing DevOps culture, DevOps in a legacy system or DevOps in Leadership to scaling DevOps, DevOps Enterprise, and ITSM and DevOps. If you’re in and around Zurich and interested in a DevOps Community, come by!
We do not want any sales pitches on our site, as we want this to be a healthy exchange of experiences and focus on the community aspect. For this reason, please contact one of the organisers before posting something on our dashboard. We will check if it complies with our guidelines and get back to you!
Dear DevOps Community
I would like to invite you to another Online Meetup. I am very happy that Baruch Sadogursky shares some DevOps patterns and antipatterns for continuous software updates with us.
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.
This talk is a collection of failure stories about software updates with advice on how to prevent those in your systems. As usual with epic failures talks, it’s educational and a lot of fun.
We’ll start by reviewing what are the driving forces behind software updates, how do we update, and why some update multiple times a day while others only update once a year. We’ll continue to review some of the epic fails, including Google WiFi, Knight Capital, CloudFlare, Jaguar and others. The patterns we are going to suggest are Canary Deployments, Observability, Local rollbacks, Feature Flags, and others.
Baruch Sadogursky - Head of DevOps Advocacy @jfrog
Baruch Sadogursky (a.k.a JBaruch) is the Head of DevOps Advocacy and a Developer Advocate at JFrog. His passion is speaking about technology. Well, speaking in general, but doing it about technology makes him look smart, and 19 years of hi-tech experience sure helps. When he’s not on stage (or on a plane to get there), he learns about technology, people and how they work, or more precisely, don’t work together.
He is a co-author of the Liquid Software book, a CNCF ambassador and a passionate conference speaker on DevOps, DevSecOps, digital transformation, containers and cloud-native, artifact management and other topics, and is a regular at the industry’s most prestigious events including KubeCon, DockerCon, Devoxx, DevOps Days, OSCON, Qcon, JavaOne and many others. You can see some of his talks at jfrog.com/shownotes
After the talk there will be enough time for questions and discussions.
19:00- 19:05: Organizer's welcome messages
19:05 - 19:45:
19:45 - : Q&A, Discussion
Looking forward seeing you :)