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
Your API ain't as secure as you think
auxesis
0
140
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
140
How to thwart your devops transformation with counterinsurgency doctrine
auxesis
1
88
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
670
Building and scaling effective distributed teams
auxesis
4
230
Mirror, mirror, on the wall
auxesis
2
290
Other Decks in Technology
See All in Technology
OpenHands🤲にContributeしてみた
kotauchisunsun
1
480
「良さそう」と「とても良い」の間には 「良さそうだがホンマか」がたくさんある / 2025.07.01 LLM品質Night
smiyawaki0820
1
390
How Community Opened Global Doors
hiroramos4
PRO
1
130
AIとともに進化するエンジニアリング / Engineering-Evolving-with-AI_final.pdf
lycorptech_jp
PRO
0
120
AIのAIによるAIのための出力評価と改善
chocoyama
2
590
5min GuardDuty Extended Threat Detection EKS
takakuni
0
160
本が全く読めなかった過去の自分へ
genshun9
0
640
KubeCon + CloudNativeCon Japan 2025 Recap Opening & Choose Your Own Adventureシリーズまとめ
mmmatsuda
0
200
あなたの声を届けよう! 女性エンジニア登壇の意義とアウトプット実践ガイド #wttjp / Call for Your Voice
kondoyuko
4
490
登壇ネタの見つけ方 / How to find talk topics
pinkumohikan
5
540
Witchcraft for Memory
pocke
1
600
Oracle Cloud Infrastructure:2025年6月度サービス・アップデート
oracle4engineer
PRO
2
290
Featured
See All Featured
The Illustrated Children's Guide to Kubernetes
chrisshort
48
50k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
507
140k
It's Worth the Effort
3n
185
28k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
29
9.5k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
35
2.4k
Art, The Web, and Tiny UX
lynnandtonic
299
21k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
32
2.3k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
29
1.8k
4 Signs Your Business is Dying
shpigford
184
22k
We Have a Design System, Now What?
morganepeng
53
7.7k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
20
1.3k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
7
710
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)