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
220
Microservices are an antipattern
Lindsay Holmwood
April 18, 2019
Tweet
Share
More Decks by Lindsay Holmwood
See All by Lindsay Holmwood
Protecting sensitive data in DynamoDB with searchable encryption
auxesis
0
14
Your API ain't as secure as you think
auxesis
0
150
Footguns and factorisation: how to make users of your cryptographic library successful
auxesis
0
1.5k
Levelling up database security by thinking in APIs
auxesis
0
140
How to thwart your devops transformation with counterinsurgency doctrine
auxesis
1
92
Mirrors, networks, and boundaries
auxesis
0
120
Managing remotely, while remotely managing
auxesis
13
4.5k
Testing Conway’s Law in open source communities
auxesis
6
690
Building and scaling effective distributed teams
auxesis
4
240
Other Decks in Technology
See All in Technology
FastAPIの魔法をgRPC/Connect RPCへ
monotaro
PRO
1
730
10年の共創が示す、これからの開発者と企業の関係 ~ Crossroad
soracom
PRO
1
170
Azure SynapseからAzure Databricksへ 移行してわかった新時代のコスト問題!?
databricksjapan
0
140
pprof vs runtime/trace (FlightRecorder)
task4233
0
160
ZOZOのAI活用実践〜社内基盤からサービス応用まで〜
zozotech
PRO
0
170
職種別ミートアップで社内から盛り上げる アウトプット文化の醸成と関係強化/ #DevRelKaigi
nishiuma
2
130
データエンジニアがこの先生きのこるには...?
10xinc
0
440
Pure Goで体験するWasmの未来
askua
1
180
空間を設計する力を考える / 20251004 Naoki Takahashi
shift_evolve
PRO
3
330
SwiftUIのGeometryReaderとScrollViewを基礎から応用まで学び直す:設計と活用事例
fumiyasac0921
0
140
Large Vision Language Modelを用いた 文書画像データ化作業自動化の検証、運用 / shibuya_AI
sansan_randd
0
100
組織観点からIAM Identity CenterとIAMの設計を考える
nrinetcom
PRO
1
170
Featured
See All Featured
Unsuck your backbone
ammeep
671
58k
GitHub's CSS Performance
jonrohan
1032
460k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
132
19k
It's Worth the Effort
3n
187
28k
Context Engineering - Making Every Token Count
addyosmani
5
180
Gamification - CAS2011
davidbonilla
81
5.5k
Stop Working from a Prison Cell
hatefulcrawdad
271
21k
Writing Fast Ruby
sferik
629
62k
Large-scale JavaScript Application Architecture
addyosmani
514
110k
Git: the NoSQL Database
bkeepers
PRO
431
66k
Side Projects
sachag
455
43k
Making Projects Easy
brettharned
119
6.4k
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)