Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
DevOps: 2009 to 2019 - 2019-09-25
Search
sullis
September 25, 2019
Programming
0
240
DevOps: 2009 to 2019 - 2019-09-25
Portland DevOps meetup
Portland Oregon
September 25, 2019
#devops
#pdxtech
sullis
September 25, 2019
Tweet
Share
More Decks by sullis
See All by sullis
Dependency Management for Java - Seattle 2025-11-18
sullis
0
38
Dependency Management for Java - Portland - 2025-11-04
sullis
0
22
Dependency management for Java applications 2025-09-11
sullis
0
33
S3 NYC Iceberg meetup 2025-07-10
sullis
0
53
Amazon S3 Chicago 2025-06-04
sullis
0
130
Amazon S3 Boston 2025-05-07
sullis
0
100
Netty ConFoo Montreal 2025-02-27
sullis
0
150
GitHub Actions ConFoo Montreal 2025-02-26
sullis
0
100
Netty Portland Java User Group 2025-02-18
sullis
0
38
Other Decks in Programming
See All in Programming
コードレビューをしない選択 #でぃーぷらすトウキョウ
kajitack
3
1k
new(1.26) ← これすき / kamakura.go #8
utgwkk
0
2.6k
Vuetify 3 → 4 何が変わった?差分と移行ポイント10分まとめ
koukimiura
0
170
Takumiから考えるSecurity_Maturity_Model.pdf
gessy0129
1
150
米国のサイバーセキュリティタイムラインと見る Goの暗号パッケージの進化
tomtwinkle
2
630
SourceGeneratorのマーカー属性問題について
htkym
0
210
メタプログラミングで実現する「コードを仕様にする」仕組み/nikkei-tech-talk43
nikkei_engineer_recruiting
0
200
CDIの誤解しがちな仕様とその対処TIPS
futokiyo
0
230
『Kubernetes ☸️ で実践する Platform Engineering 』を最高速度で読み抜いたる!!👊🏻
hiroki_hasegawa
0
100
ベクトル検索のフィルタを用いた機械学習モデルとの統合 / python-meetup-fukuoka-06-vector-attr
monochromegane
2
500
CSC307 Lecture 14
javiergs
PRO
0
480
ロボットのための工場に灯りは要らない
watany
11
3.1k
Featured
See All Featured
Accessibility Awareness
sabderemane
0
84
How to Think Like a Performance Engineer
csswizardry
28
2.5k
Claude Code のすすめ
schroneko
67
220k
Building Better People: How to give real-time feedback that sticks.
wjessup
370
20k
The Invisible Side of Design
smashingmag
302
51k
Deep Space Network (abreviated)
tonyrice
0
93
What’s in a name? Adding method to the madness
productmarketing
PRO
24
4k
Neural Spatial Audio Processing for Sound Field Analysis and Control
skoyamalab
0
230
Design in an AI World
tapps
0
180
Navigating Algorithm Shifts & AI Overviews - #SMXNext
aleyda
1
1.2k
A brief & incomplete history of UX Design for the World Wide Web: 1989–2019
jct
1
330
Hiding What from Whom? A Critical Review of the History of Programming languages for Music
tomoyanonymous
2
570
Transcript
DevOps 2009 to 2019 Sean Sullivan Portland DevOps meetup September
25, 2019
About me: Scala Java Kotlin Python
deleted scenes
Linux could be most aptly described as agrarian pre-capitalist
Ubuntu
Dev Ops
YAML
YAML Docker
DevOps YAML Docker Kubernetes
Twitter
None
None
None
None
June 2009
None
None
Paul Hammond John Allspaw
None
None
None
None
None
None
None
None
None
None
None
None
Flickr could be most aptly described as agrarian pre-DevOps
2010
None
“Create a repeatable, reliable process for releasing software”
“If it hurts, do it more frequently, and bring the
pain forward.”
“If releasing software is painful, aim to release it every
time somebody checks in a change that passes all the automated tests.”
“a deployment pipeline is an automated manifestation of your process
for getting software from version control into the hands of your users”
2018
None
“The findings from our research show clearly that the value
of adopting DevOps is even larger than we had initially thought”
“the gap between high and low performers continues to grow”
Software delivery performance: 1. Lead Time 2. Deployment Frequency 3.
Mean Time to Restore (MTTR) 4. Change Fail Percentage
2019
None
“Most companies don’t include their databases in their DevOps practices”
“A key part of DevOps for the database is to
recognize that this schema is code”
“[the database schema] should be stored in source control, and
subject to the same processes and controls as application source code”
“you need to be able to upgrade the database schema
without breaking the application”
“you also need to be able to upgrade the application
and run it against an old schema version”
Postgres could be most aptly described as agrarian NoSQL
None
“speed and stability are both possible”
Software delivery and operational performance: 1. Lead Time 2. Deployment
Frequency 3. Mean Time to Restore (MTTR) 4. Change Fail Percentage 5. Availability
Elite performers: 208 times more frequent code deployments 2604 times
faster time to recover from incidents
DevOps could be most aptly described as decentralized cat herding
DevOps
Thank you! tinyrobots
DevOps