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
240
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
74
Get up to speed with DevOps
erwinstaal
0
44
Event-driven autoscaling on Kubernetes with KEDA and Azure Functions
erwinstaal
0
220
DevOps - The Automation op compliance
erwinstaal
0
140
Get up to speed with DevOps
erwinstaal
0
52
Get up to speed with DevOps using modern development practices
erwinstaal
0
78
TechDaysNL - De tien fundamenten van Continuous Delivery
erwinstaal
0
98
Microsoft Unity
erwinstaal
0
88
De 10 geboden van Continuous Delivery
erwinstaal
0
110
Other Decks in Technology
See All in Technology
AI時代だからこそ考える、僕らが本当につくりたいスクラムチーム / A Scrum Team we really want to create in this AI era
takaking22
7
4k
Access-what? why and how, A11Y for All - Nordic.js 2025
gdomiciano
1
120
綺麗なデータマートをつくろう_データ整備を前向きに考える会 / Let's create clean data mart
brainpadpr
3
370
やる気のない自分との向き合い方/How to Deal with Your Unmotivated Self
sanogemaru
0
450
Git in Team
kawaguti
PRO
3
330
AI時代こそ求められる設計力- AWSクラウドデザインパターン3選で信頼性と拡張性を高める-
kenichirokimura
3
250
衛星画像超解像化によって実現する2D, 3D空間情報の即時生成と“AI as a Service”/ Real-time generation spatial data enabled_by satellite image super-resolution
lehupa
0
120
セキュアな認可付きリモートMCPサーバーをAWSマネージドサービスでつくろう! / Let's build an OAuth protected remote MCP server based on AWS managed services
kaminashi
3
270
Adminaで実現するISMS/SOC2運用の効率化 〜 アカウント管理編 〜
shonansurvivors
4
430
許しとアジャイル
jnuank
1
140
extension 現場で使えるXcodeショートカット一覧
ktombow
0
220
職種別ミートアップで社内から盛り上げる アウトプット文化の醸成と関係強化/ #DevRelKaigi
nishiuma
2
160
Featured
See All Featured
GraphQLとの向き合い方2022年版
quramy
49
14k
GitHub's CSS Performance
jonrohan
1032
470k
Measuring & Analyzing Core Web Vitals
bluesmoon
9
620
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
19
1.2k
Build your cross-platform service in a week with App Engine
jlugia
232
18k
The Web Performance Landscape in 2024 [PerfNow 2024]
tammyeverts
9
860
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
358
30k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
162
15k
Product Roadmaps are Hard
iamctodd
PRO
54
11k
How STYLIGHT went responsive
nonsquared
100
5.8k
Stop Working from a Prison Cell
hatefulcrawdad
271
21k
Code Review Best Practice
trishagee
72
19k
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