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
Architecting for Continuous Delivery
Search
Erwin Staal
February 28, 2019
Technology
0
230
Architecting for Continuous Delivery
Erwin Staal
February 28, 2019
Tweet
Share
More Decks by Erwin Staal
See All by Erwin Staal
Networking on Azure PaaS
erwinstaal
0
70
Get up to speed with DevOps
erwinstaal
0
40
Event-driven autoscaling on Kubernetes with KEDA and Azure Functions
erwinstaal
0
200
DevOps - The Automation op compliance
erwinstaal
0
130
Get up to speed with DevOps
erwinstaal
0
51
Get up to speed with DevOps using modern development practices
erwinstaal
0
76
TechDaysNL - De tien fundamenten van Continuous Delivery
erwinstaal
0
95
Microsoft Unity
erwinstaal
0
85
De 10 geboden van Continuous Delivery
erwinstaal
0
110
Other Decks in Technology
See All in Technology
american aa airlines®️ USA Contact Numbers: Complete 2025 Support Guide
aaguide
0
500
Enhancing SaaS Product Reliability and Release Velocity through Optimized Testing Approach
ropqa
1
250
第64回コンピュータビジョン勉強会「The PanAf-FGBG Dataset: Understanding the Impact of Backgrounds in Wildlife Behaviour Recognition」
x_ttyszk
0
170
データ基盤からデータベースまで?広がるユースケースのDatabricksについて教えるよ!
akuwano
3
160
DBのスキルで生き残る技術 - AI時代におけるテーブル設計の勘所
soudai
PRO
55
22k
AWS CDK 開発を成功に導くトラブルシューティングガイド
wandora58
3
170
全部AI、全員Cursor、ドキュメント駆動開発 〜DevinやGeminiも添えて〜
rinchsan
2
2.2k
SEQUENCE object comparison - db tech showcase 2025 LT2
nori_shinoda
0
280
ソフトウェアQAがハードウェアの人になったの
mineo_matsuya
3
110
CDK Vibe Coding Fes
tomoki10
1
530
[ JAWS-UG千葉支部 x 彩の国埼玉支部 ]ムダ遣い卒業!FinOpsで始めるAWSコスト最適化の第一歩
sh_fk2
2
150
関数型プログラミングで 「脳がバグる」を乗り越える
manabeai
2
220
Featured
See All Featured
Code Review Best Practice
trishagee
69
19k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
138
34k
Designing for Performance
lara
610
69k
Build your cross-platform service in a week with App Engine
jlugia
231
18k
A Tale of Four Properties
chriscoyier
160
23k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
3.1k
Measuring & Analyzing Core Web Vitals
bluesmoon
7
510
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
29
9.6k
Building Adaptive Systems
keathley
43
2.7k
The Illustrated Children's Guide to Kubernetes
chrisshort
48
50k
Stop Working from a Prison Cell
hatefulcrawdad
271
21k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
10
970
Transcript
Architecting for Continuous Delivery Erwin Staal | 4DotNet | @erwin_staal
Software Engineer 4DotNet @erwin_staal Erwin Staal
How do we architect for Continuous Delivery?
The ability to get changes—features, configuration changes, bug fixes and
experiments—into production, or into the hands of users, safely and quickly in a sustainable way Jez Humble - Author of ‘Continuous Delivery’
State of DevOps Report 2018
The two rules Everyone is checking into trunk daily (at
least) Software (trunk) is always deployable
Foundations Configuration management Continuous integration (CI) Continuous testing
None
Portability Testability Scalability Security Maintainability Usability Availability Personalizability Responsiveness Upgradability
Extensibility Flexibility Deployability
Deployability Testability
Operations at web scale is the ability to consistently create
and deploy reliable software to an unreliable platform that scales horizontally Jesse Robbins - former ‘Master of Disaster’ @ Amazon
CAP Theorem Eric Brewers
Operations at web scale is the ability to consistently create
and deploy reliable software to an unreliable platform that scales horizontally Jesse Robbins - former ‘Master of Disaster’ @ Amazon
Decomposition of systems
Component / service Part of your system that could be
swapped out for another implementation Martin Fowler
Component / service Make system more maintainable (better encapsulation, lower
coupling) Make system easier to build and test Enable collaboration (one team per service)
Bind components at Run Time (Microservice) Independent deployment Use cluster
infrastructure Kubernetes, Service Fabric, … Don’t break downstream API versioning Blue / Green deployment Cater for failure in downstream system Circuit breaker Retry pattern Monitoring is complex
Bind components at Build Time (Monolith) Google, Facebook, Etsy Continuous
Integration at scale
Architecture evolves
Monolith First Martin Fowler
Microservice Monolith Productivity Complexity
None
Strangler application
None
Erwin Staal @erwin_staal https://www.linkedin.com/in/erwinstaal/ Contact