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
3 surprises when Continuously Deploying infrast...
Search
Lindsay Holmwood
April 16, 2015
Technology
0
120
3 surprises when Continuously Deploying infrastructure
Lindsay Holmwood
April 16, 2015
Tweet
Share
More Decks by Lindsay Holmwood
See All by Lindsay Holmwood
Your API ain't as secure as you think
auxesis
0
140
Footguns and factorisation: how to make users of your cryptographic library successful
auxesis
0
1.4k
Levelling up database security by thinking in APIs
auxesis
0
140
How to thwart your devops transformation with counterinsurgency doctrine
auxesis
1
90
Microservices are an antipattern
auxesis
0
220
Mirrors, networks, and boundaries
auxesis
0
120
Managing remotely, while remotely managing
auxesis
13
4.5k
Testing Conway’s Law in open source communities
auxesis
6
680
Building and scaling effective distributed teams
auxesis
4
230
Other Decks in Technology
See All in Technology
Transformerを用いたアイテム間の 相互影響を考慮したレコメンドリスト生成
recruitengineers
PRO
2
440
Deep Security Conference 2025:生成AI時代のセキュリティ監視 /dsc2025-genai-secmon
mizutani
4
2.9k
How Do I Contact Jetblue Airlines® Reservation Number: Fast Support Guide
thejetblueairhelpsupport
0
150
VS CodeとGitHub Copilotで爆速開発!アップデートの波に乗るおさらい会 / Rapid Development with VS Code and GitHub Copilot: Catch the Latest Wave
yamachu
3
460
大量配信システムにおけるSLOの実践:「見えない」信頼性をSLOで可視化
plaidtech
PRO
0
390
毎晩の 負荷試験自動実行による効果
recruitengineers
PRO
5
180
united airlines ™®️ USA Contact Numbers: Complete 2025 Support Guide
flyunitedhelp
1
470
名刺メーカーDevグループ 紹介資料
sansan33
PRO
0
820
第64回コンピュータビジョン勉強会「The PanAf-FGBG Dataset: Understanding the Impact of Backgrounds in Wildlife Behaviour Recognition」
x_ttyszk
0
240
AI時代にも変わらぬ価値を発揮したい: インフラ・クラウドを切り口にユーザー価値と非機能要件に向き合ってエンジニアとしての地力を培う
netmarkjp
0
130
マルチプロダクト環境におけるSREの役割 / SRE NEXT 2025 lunch session
sugamasao
1
730
CDKコード品質UP!ナイスな自作コンストラクタを作るための便利インターフェース
harukasakihara
2
230
Featured
See All Featured
A better future with KSS
kneath
238
17k
Optimizing for Happiness
mojombo
379
70k
Automating Front-end Workflow
addyosmani
1370
200k
StorybookのUI Testing Handbookを読んだ
zakiyama
30
5.9k
Building an army of robots
kneath
306
45k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
3.1k
The Cost Of JavaScript in 2023
addyosmani
51
8.6k
Practical Orchestrator
shlominoach
189
11k
Code Reviewing Like a Champion
maltzj
524
40k
The Straight Up "How To Draw Better" Workshop
denniskardys
235
140k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
357
30k
Stop Working from a Prison Cell
hatefulcrawdad
271
21k
Transcript
3 surprises when Continuously Deploying infrastructure
What is Continuously Deployed infrastructure?
code change CI running infrastructure
Fast feedback is key
Get iteration time down
< 5 minutes
Track cycle time (min, max, median, 95e)
Get CI close to the action
Eliminate latency
Chunk your changes
Change one, Test one
Make it work Make it right Make it fast
Make it work Make it fast Make it right
1. Validate idea 2. Pay off technical debt
Consider eliminating gates
idea production
Staging slows feedback
1. Extra tasks every change 2. Less changes pushed into
production 3. Lingering state 4. Higher costs
BUT it can provide high quality feedback
1. Your changes must apply faster 2. 80% coverage is
good enough
Don’t start with a staging environment
Find other ways to detect errors
Think fast and slow
Fast tests
Smoke tests
< 10 seconds
Change one, Test one
1. Change app 2. Change DB 3. Change proxy 4.
Test app 5. Test DB 6. Test proxy 4. Test app 5. Test DB 6. Test proxy
1. Change app 2. Test app 3. Change DB 4.
Test DB 5. Change proxy 6. Test proxy fail early 1. Change app 2. Test app 3. Change DB 4. Test DB 5. Change proxy 6. Test proxy
Make feedback visual
None
Slow tests
Full stack Integration tests
Things you should test
Flow of data
Example: - Change DNS record - Check record after TTL
Simulated client interactions
Example (AP): - Write data to store - Query each
node has data within n seconds
Hook into monitoring
Example: - CI runs slow tests - Monitoring queries CI
Ship monitoring with code
Expose discoverable endpoints
Biggest surprise?
Actually possible
Push all changes through CI
More visibility
Faster to change Faster to fix
Thank you! Questions?