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
180
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
110
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
110
How to thwart your devops transformation with counterinsurgency doctrine
auxesis
1
71
Mirrors, networks, and boundaries
auxesis
0
85
Managing remotely, while remotely managing
auxesis
13
4.2k
Testing Conway’s Law in open source communities
auxesis
6
540
Building and scaling effective distributed teams
auxesis
4
200
Mirror, mirror, on the wall
auxesis
2
270
Other Decks in Technology
See All in Technology
App Router を実プロダクトで採用して見えてきた勘所をちょっとだけ紹介
marokanatani
1
930
GC24 Recap: Interface Internals
task4233
0
150
効果的なオンコール対応と障害対応
ryuichi1208
6
3.1k
Cloud Run と GitHub Template Repository による軽量なアプリケーションプラットフォーム/ #nikkei_tech_talk
nikkei_engineer_recruiting
0
110
言葉は感情の近似値である。その感情と言葉の誤差を最小化しよう ~コミュニケーションにおけるアナログ/デジタル変換の課題に立ち向かう~
nktamago
0
230
Oracle Base Database Service 技術詳細
oracle4engineer
PRO
5
46k
OSTという文化を組織に根付かせてみた
sansantech
PRO
2
390
突撃! 隣のAmazon Bedrockユーザー 〜YouはどうしてAWSで?〜
minorun365
PRO
3
390
やってやろうじゃないかメカアジャイル! / Let's do it, mechanical agile!
psj59129
1
670
「家族アルバム みてね」における運用管理・ オブザーバビリティの全貌 / Overview of Operation Management and Observability in FamilyAlbum
isaoshimizu
4
160
『GRANBLUE FANTASY Relink』ソフトウェアラスタライザによる実践的なオクルージョンカリング
cygames
0
170
React Aria で実現する次世代のアクセシビリティ
ryo_manba
4
1.2k
Featured
See All Featured
Unsuck your backbone
ammeep
667
57k
Build The Right Thing And Hit Your Dates
maggiecrowley
30
2.3k
Raft: Consensus for Rubyists
vanstee
135
6.5k
The Language of Interfaces
destraynor
153
23k
Designing for humans not robots
tammielis
248
25k
Designing on Purpose - Digital PM Summit 2013
jponch
114
6.8k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
29
2.6k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
166
48k
The Brand Is Dead. Long Live the Brand.
mthomps
53
38k
Speed Design
sergeychernyshev
22
430
RailsConf 2023
tenderlove
28
810
Atom: Resistance is Futile
akmur
261
25k
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)