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
Patterns for treating infrastructure as code
Search
Andrew Crump
May 09, 2013
Programming
1
300
Patterns for treating infrastructure as code
London Continuous Delivery Meetup - 9th May 2013
Andrew Crump
May 09, 2013
Tweet
Share
More Decks by Andrew Crump
See All by Andrew Crump
Porting a small project from Go to Rust
acrmp
0
15
Docker and Cloud Foundry
acrmp
0
110
Extending Foodcritic with new rules
acrmp
2
660
Continuous Delivery with Cloud Foundry
acrmp
1
110
Other Decks in Programming
See All in Programming
1から理解するWeb Push
dora1998
7
1.9k
testingを眺める
matumoto
1
140
より安全で効率的な Go コードへ: Protocol Buffers Opaque API の導入
shwatanap
2
740
GitHubとGitLabとAWS CodePipelineでCI/CDを組み比べてみた
satoshi256kbyte
4
250
The Past, Present, and Future of Enterprise Java
ivargrimstad
0
410
Navigating Dependency Injection with Metro
zacsweers
3
2.5k
ユーザーも開発者も悩ませない TV アプリ開発 ~Compose の内部実装から学ぶフォーカス制御~
taked137
0
190
さようなら Date。 ようこそTemporal! 3年間先行利用して得られた知見の共有
8beeeaaat
3
1.5k
ファインディ株式会社におけるMCP活用とサービス開発
starfish719
0
2k
Tool Catalog Agent for Bedrock AgentCore Gateway
licux
7
2.5k
JSONataを使ってみよう Step Functionsが楽しくなる実践テクニック #devio2025
dafujii
1
630
Zendeskのチケットを Amazon Bedrockで 解析した
ryokosuge
3
320
Featured
See All Featured
Designing Dashboards & Data Visualisations in Web Apps
destraynor
231
53k
Raft: Consensus for Rubyists
vanstee
140
7.1k
Done Done
chrislema
185
16k
4 Signs Your Business is Dying
shpigford
184
22k
Context Engineering - Making Every Token Count
addyosmani
3
58
How to Think Like a Performance Engineer
csswizardry
26
1.9k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
30
9.7k
Why You Should Never Use an ORM
jnunemaker
PRO
59
9.5k
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
26
3k
Typedesign – Prime Four
hannesfritz
42
2.8k
Facilitating Awesome Meetings
lara
55
6.5k
How GitHub (no longer) Works
holman
315
140k
Transcript
Patterns for treating infrastructure as code #londoncd
@acrmp
"Enable the reconstruction of the business from nothing but a
source code repository, an application data backup, and bare metal resources." - John Allspaw and Jesse Robbins, Web Operations
#1 Include infrastructure code in your pipeline
None
Bring your infrastructure and application pipelines together
Application Code Infrastructure Code Base OS
Rebuild when other layers change
#2 Treat individual modules as software projects
None
Separate code repo
Use a tool to manage module dependencies
#3 Avoid making manual changes
None
code -> build -> binary
code -> converge -> node
Reproducible
Metrics
#4 Aggressively chase fast feedback
None
Parallelise
realness -> time ->
Well-formedness check
Static code analysis
Unit Testing
None
Integration Tests
Converge and reconverge
Lightweight Virtualisation
#5 Vendor your dependencies
None
Caching Proxy
Build in a off-network environment
Schedule Builds
Automate population of your artefact repo
#6 Define your complete environment in a declarative manifest
None
Use services that expose an API
Dumb Orchestration
Thanks!