DevOps Patterns & Antipatterns for Continuous Software Updates

A presentation at Downtown San Jose DevOps Meetup July 2020 in July 2020 in San Jose, CA, USA by Baruch Sadogursky

Slide 1

Slide 1

DevOps Patterns & Antipatterns for Continuous Software Updates “What can possibly go wrong?!”

Slide 2

Slide 2

Why software updates?

Slide 3

Slide 3

@jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 4

Slide 4

Slide 5

Slide 5

Slide 6

Slide 6

@jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 7

Slide 7

“As every company become a software company, Security vulnerabilities are the new oil spills” @jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 8

Slide 8

Slide 9

Slide 9

Identify @jbaruch Fix #LiquidSoftware Deploy http://jfrog.com/shownotes

Slide 10

Slide 10

Identify Immediately Fix OS upgrade Deploy years

Slide 11

Slide 11

Identify Fix Deploy 2 months Struts upgrade 2 months

Slide 12

Slide 12

@jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 13

Slide 13

@jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 14

Slide 14

@jbaruch #LiquidSoftware Identify As fast as possible Fix As fast as possible Deploy As fast as possible http://jfrog.com/shownotes

Slide 15

Slide 15

Slide 16

Slide 16

Slide 17

Slide 17

Slide 18

Slide 18

@jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 19

Slide 19

This is not a new idea! @jbaruch XP: short feedback Scrum: reducing cycle time to absolute minimum TPS: Decide as late as possible and Deliver as fast as possible Kanban: Incremental change #LiquidSoftware http://jfrog.com/shownotes

Slide 20

Slide 20

Slide 21

Slide 21

🎩 @jbaruch #dockercon jfrog.com/shownotes @ErinMeyerINSEAD’s “Culture Map”

Slide 22

Slide 22

shownotes http://jfrog.com/shownotes Slides Video Links Comments, Ratings Raffle @jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 23

Slide 23

Slide 24

Slide 24

@jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 25

Slide 25

@jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 26

Slide 26

Slide 27

Slide 27

@jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 28

Slide 28

Update available Yes No Do we trust the update? Yes How about no Let’s update! Yes Are there any high risks? No Do we want it? No

Slide 29

Slide 29

@jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 30

Slide 30

number of artifacts as a symptom of complexity Today IoT Serverless Docker Microservices Infrastructure as Code Continuous Delivery Continuous Integration Agile 2000 @jbaruch @jfrog #LiquidSoftware www.liquidsoftware.com

Slide 31

Slide 31

The problem is not the code, it’s the data. Big data. @jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 32

Slide 32

Update available Yes No Can we verify the update? No Yes Yes How about no Do we trust the update? Time consuming verification Let’s update! Yes Are there any high risks? No Do we want it? No

Slide 33

Slide 33

Slide 34

Slide 34

Features that we want @jbaruch Acceptance tests costs #LiquidSoftware http://jfrog.com/shownotes

Slide 35

Slide 35

Slide 36

Slide 36

Your browser Twitter in your browser Twitter on your smartphone Your smartphone OS?! Update available Yes Are there any high risks? No Let’s update! Do we want it? No one asked you (auto update)

Slide 37

Slide 37

What can possibly go wrong?

Slide 38

Slide 38

@jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 39

Slide 39

Slide 40

Slide 40

Continuous updates pattern: Local rollback @jbaruch Problem: update went catastrophically wrong and an over the-air patch can’t reach the device Solution: Have a previous version saved on the device prior to update. Rollback in case problem occurred #LiquidSoftware http://jfrog.com/shownotes

Slide 41

Slide 41

@jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 42

Slide 42

Slide 43

Slide 43

Slide 44

Slide 44

Slide 45

Slide 45

Continuous updates pattern: OTA software updates @jbaruch Problem: physical recalls are costly. Extremely costly. Also, you can’t force an upgrade. Solution: Implement over the air software updates, preferably, continuous updates. #LiquidSoftware http://jfrog.com/shownotes

Slide 46

Slide 46

continuous OTA updates are like normal OTA updates, but better @jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 47

Slide 47

Slide 48

Slide 48

Slide 49

Slide 49

Continuous updates pattern: continuous updates @jbaruch Problem: In batch updates important features wait for non-important features. Solution: Implement continuous updates. #LiquidSoftware http://jfrog.com/shownotes

Slide 50

Slide 50

You thought your problems are hard? Things under your control ✓ ✓ ✓ ✓ The availability of the target The state of the target The version on the target The access to the target @jbaruch Server-side Updates #LiquidSoftware http://jfrog.com/shownotes IoT (Mobile, Automotive, Edge) Updates ✕ ✕ ✕ ✕

Slide 51

Slide 51

Slide 52

Slide 52

KNIGHT-MARE @jbaruch New system reused old APIs 1 out of 8 servers was not updated New clients sent requests to machine contained old code Engineers undeployed working code from updated servers, increasing the load on the not-updated server No monitoring, no alerting, no debugging #LiquidSoftware http://jfrog.com/shownotes

Slide 53

Slide 53

Continuous updates pattern: Automated deployment @jbaruch Problem: People suck at repetitive tasks. Solution: Automate everything. #LiquidSoftware http://jfrog.com/shownotes

Slide 54

Slide 54

Continuous updates pattern: frequent updates @jbaruch Problem: Seldom deployments generate anxiety and stress, leading to errors. Solution: Update frequently to develop skill and habit. #LiquidSoftware http://jfrog.com/shownotes

Slide 55

Slide 55

Continuous updates pattern: state awareness @jbaruch Problem: Target state can affect the update process and the behavior of the system after the update. Solution: Know and consider target state when updating. Reverting might require revering the state. #LiquidSoftware http://jfrog.com/shownotes

Slide 56

Slide 56

Slide 57

Slide 57

Cloud-dark @jbaruch New rules are deployed frequently to battle attacks Deployment of a single misconfigured rule Included regex to spike CPU to 100% “Affected region: Earth” #LiquidSoftware http://jfrog.com/shownotes

Slide 58

Slide 58

Continuous updates pattern: Progressive Delivery @jbaruch Problem: Releasing a bug affects ALL the users. Solution: Release to a small number of users first effectively reducing the blast radius and observe. If a problem occurs, stop the release, revert or update the affected users. #LiquidSoftware http://jfrog.com/shownotes

Slide 59

Slide 59

@jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 60

Slide 60

Continuous updates pattern: observability @jbaruch Problem: Some problems are hard to trace relying on user feedback only Solution: Implement tracing, monitoring and logging #LiquidSoftware http://jfrog.com/shownotes

Slide 61

Slide 61

Continuous updates pattern: Rollbacks @jbaruch Problem: Fixes might take time, users suffer in a meanwhile Solution: Implement rollback, the ability to deploy a previous version without delay #LiquidSoftware http://jfrog.com/shownotes

Slide 62

Slide 62

Continuous updates pattern: feature flags @jbaruch Problem: Rollbacks are not always supported by the deployment target platform Solution: Embed 2 versions of the features in the app itself and trigger them with API calls #LiquidSoftware http://jfrog.com/shownotes

Slide 63

Slide 63

@jbaruch #LiquidSoftware #DevOpsTO http://jfrog.com/shownotes

Slide 64

Slide 64

Cloud-dark (the sequel) While doing maintenance on Newark->Chicago segment, engineers wanted to route that traffic through Atlanta They updated the config manually They routed ALL THE TRAFFIC through Atlanta instead Atlanta crashed, in chain reaction everything else crashed as well “Affected region: Earth” @jbaruch #LiquidSoftware #DevOpsTO http://jfrog.com/shownotes

Slide 65

Slide 65

Continuous updates pattern: Automated deployment @jbaruch Problem: People suck at repetitive tasks. Solution: Automate everything. #LiquidSoftware http://jfrog.com/shownotes

Slide 66

Slide 66

Slide 67

Slide 67

Continuous updates pattern: zero downtime updates @jbaruch Problem: You will probably loose all your users if you shut down for 5 weeks to perform an update. Solution: Perform zerodowntime OTA small and fequent continuous updates. #LiquidSoftware http://jfrog.com/shownotes

Slide 68

Slide 68

Continuous updates @jbaruch Frequent Automatic Tested Progressively delivered State-aware Observability *Local Rollbacks #LiquidSoftware http://jfrog.com/shownotes

Slide 69

Slide 69

Update available Yes Do we trust the update? Yes Do we want it? Are there any high risks? Sure, why not? (auto update) Yes Let’s update! No

Slide 70

Slide 70

” Our goal is to transition from bulk and rare software updates to extremely tiny and extremely frequent software updates; so tiny and so frequent that they provide an illusion of software flowing from development to the update target. We call it the Liquid Software vision. @jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 71

Slide 71

@jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 72

Slide 72

Corner cases? @jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 73

Slide 73

Slide 74

Slide 74

Slide 75

Slide 75

@jbaruch #LiquidSoftware http://jfrog.com/shownotes

Slide 76

Slide 76

@jbaruch Q&A and twitter ads #LiquidSoftware https://liquidsoftware.com https://jfrog.com/shownotes