Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Speaker Deck
PRO
Sign in
Sign up for free
Microservices are an antipattern
Lindsay Holmwood
April 18, 2019
Technology
0
140
Microservices are an antipattern
Lindsay Holmwood
April 18, 2019
Tweet
Share
More Decks by Lindsay Holmwood
See All by Lindsay Holmwood
Footguns and factorisation: how to make users of your cryptographic library successful
auxesis
0
1.1k
Levelling up database security by thinking in APIs
auxesis
0
63
How to thwart your devops transformation with counterinsurgency doctrine
auxesis
1
45
Mirrors, networks, and boundaries
auxesis
0
62
Managing remotely, while remotely managing
auxesis
13
3.5k
Testing Conway’s Law in open source communities
auxesis
6
370
Building and scaling effective distributed teams
auxesis
4
150
Mirror, mirror, on the wall
auxesis
2
240
Mixing oil and water: devops in an ITSM world
auxesis
1
380
Other Decks in Technology
See All in Technology
ISUCON で使えるツールを作った
shotakitazawa
0
350
AWS全体のセキュリティ管理と快適なセキュリティ運用
cmusudakeisuke
2
10k
220428event_ogura_part
caddi_eng
0
170
【OCHaCafe#5】その Pod 突然落ちても大丈夫ですか?
k6s4i53rx
2
110
Power BI Report Ops
hanaseleb
0
140
Power Query 日時の変換でちょっと焦ったケース +1 / Power Query Some cases
ishiayaya
0
140
目と耳を持った自然言語処理 - スタートアップにおける価値創出のために
yag_ays
PRO
0
500
Babylon.js v5 新機能の紹介
limes2018
0
320
HTTP Session Architecture Pattern
chiroito
1
320
How We Foster Reliability in Diversity
nari_ex
PRO
8
1.7k
1年間のポストモーテム運用とそこから生まれたツール sre-advisor / SRE NEXT 2022
fujiwara3
5
2.3k
プロダクトグロースと技術のベースアップを両立させるRettyのアプリ開発スタイル / Achieve Product Growth and Tech Update
imaizume
1
250
Featured
See All Featured
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
29
4.3k
jQuery: Nuts, Bolts and Bling
dougneiner
56
6.4k
Making the Leap to Tech Lead
cromwellryan
113
6.9k
Automating Front-end Workflow
addyosmani
1351
200k
Clear Off the Table
cherdarchuk
79
280k
A Modern Web Designer's Workflow
chriscoyier
689
180k
Facilitating Awesome Meetings
lara
29
3.9k
KATA
mclloyd
7
8.5k
ParisWeb 2013: Learning to Love: Crash Course in Emotional UX Design
dotmariusz
100
5.9k
Docker and Python
trallard
27
1.5k
Build your cross-platform service in a week with App Engine
jlugia
219
17k
5 minutes of I Can Smell Your CMS
philhawksworth
196
18k
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)