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
Microservices are an antipattern
Search
Lindsay Holmwood
April 18, 2019
Technology
0
210
Microservices are an antipattern
Lindsay Holmwood
April 18, 2019
Tweet
Share
More Decks by Lindsay Holmwood
See All by Lindsay Holmwood
Your API ain't as secure as you think
auxesis
0
130
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
130
How to thwart your devops transformation with counterinsurgency doctrine
auxesis
1
82
Mirrors, networks, and boundaries
auxesis
0
110
Managing remotely, while remotely managing
auxesis
13
4.4k
Testing Conway’s Law in open source communities
auxesis
6
640
Building and scaling effective distributed teams
auxesis
4
220
Mirror, mirror, on the wall
auxesis
2
280
Other Decks in Technology
See All in Technology
新卒エンジニアがCICDをモダナイズしてみた話
akashi_sn
2
240
CloudWatch 大好きなSAが語る CloudWatch キホンのキ
o11yfes2023
0
180
彩の国で始めよう。おっさんエンジニアから共有したい、当たり前のことを当たり前にする技術
otsuki
0
150
Creating Awesome Change in SmartNews
martin_lover
1
280
Would you THINK such a demonstration interesting ?
shumpei3
1
220
ワールドカフェI /チューターを改良する / World Café I and Improving the Tutors
ks91
PRO
0
120
バクラクの認証基盤の成長と現在地 / bakuraku-authn-platform
convto
1
540
開発視点でAWS Signerを考えてみよう!! ~コード署名のその先へ~
masakiokuda
3
170
いつも初心者向けの記事に助けられているので得意分野では初心者向けの記事を書きます
toru_kubota
2
320
食べログが挑む!飲食店ネット予約システムで自動テスト無双して手動テストゼロを実現する戦略
hagevvashi
3
420
ブラウザのレガシー・独自機能を愛でる-Firefoxの脆弱性4選- / Browser Crash Club #1
masatokinugawa
1
470
はてなの開発20年史と DevOpsの歩み / DevOpsDays Tokyo 2025 Keynote
daiksy
6
1.5k
Featured
See All Featured
VelocityConf: Rendering Performance Case Studies
addyosmani
328
24k
A better future with KSS
kneath
239
17k
Six Lessons from altMBA
skipperchong
27
3.7k
A Modern Web Designer's Workflow
chriscoyier
693
190k
For a Future-Friendly Web
brad_frost
176
9.7k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
251
21k
Fantastic passwords and where to find them - at NoRuKo
philnash
51
3.1k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
178
53k
The Power of CSS Pseudo Elements
geoffreycrofte
75
5.8k
Rebuilding a faster, lazier Slack
samanthasiow
80
8.9k
We Have a Design System, Now What?
morganepeng
52
7.5k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
45
7.2k
Transcript
Microservices are an antipattern Lindsay Holmwood
Microservices are an antipattern Lindsay Holmwood
Why microservices?
Design strategy to manage complexity in our systems
Design strategy to manage complexity in our systems
If the system or team get too big, we: 1.
Split the system
If the system or team get too big, we: 1.
Split the system
If the system or team get too big, we: 2.
Split the team
Popularised by the devops movement
Popularised by the devops movement
CD + containers were the drivers
CD + containers were the drivers
In use at the big end of town
“It works for Google, so we’ll scale it down and
get the same benefits!”
We cargo culted a design strategy without understanding the tradeoffs
Real talk: The smallest microservice at Google probably does more
transactions than the largest service in your organisation.
Real talk: We took a pattern for managing huge systems,
extrapolated it down to our size, and hoped it worked.
Real talk: Hope is not a strategy.
Some downsides you should think about:
Some downsides you should think about:
You’re replacing function calls with network calls
Source: “Systems Performance: Enterprise and the Cloud” by Brendan Gregg
Is that latency worth it?
What hard limits are you imposing to control unpredictability?
Microservices are a systems multiplier for your shitty code
None
How is your ◦ modularity? ◦ isolation? ◦ encapsulation?
Refactor first
Then scale when the performance impacts users
1. Make it work 2. Make it right 3. Make
it fast
1. Make it work 2. Make it right 3. Make
it fast Refactor
1. Make it work 2. Make it right 3. Make
it fast Refactor Microservice
Microservices have a higher cost of ownership
Operational requirements: ◦ CD pipelines ◦ Network & compute &
storage ◦ Logging ◦ Monitoring ◦ Tracing & observability
Security requirements: ◦ Authentication ◦ Identity ◦ Monitoring
This costs more (both in systems bills and engineering time)
But what if we just… didn’t?
But what if we just… didn’t?
Problems are harder to debug
Incidents have > MTTD & MTTR
Delivery slows
Increased communication + coordination overhead between teams
Sequencing of changes across multiple services
Poor service boundaries? You have to get multiple teams moving
in the same direction to deliver a change.
Stakeholders for technical changes are rarely exclusively technical
Requires coordination across disciplines like product, design, marketing, analytics, …
You need established and understood communication paths
You need established and understood change coordination
You need established cultural norms for resolving conflict
Microservices are an effective way to separate concerns in complex
systems
Microservices are an inefficient way of organising people in organisations
< 1,000 people
The smaller the org, the smaller the return
You are not Google/Netflix/ AWS/Facebook/…
Do the job you have, not the job you want.
Thank you! (fight me)