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
The 7 Deadly Sins of Microservices
Search
Tareq Abedrabbo
November 27, 2014
Technology
7
1.2k
The 7 Deadly Sins of Microservices
MuCon 2014
Tareq Abedrabbo
November 27, 2014
Tweet
Share
More Decks by Tareq Abedrabbo
See All by Tareq Abedrabbo
Not a SO(A) Trivial Question!
tareqabedrabbo
0
61
Designing APIs for Data Driven Systems
tareqabedrabbo
0
56
Things I wish I'd known before I started with Microservices
tareqabedrabbo
0
660
Building a Scalable Event Service with Cassandra: Design to Code
tareqabedrabbo
1
470
The Ubiquitous Graph
tareqabedrabbo
0
200
The 7 Deadly Sins of Microservices
tareqabedrabbo
0
610
Building a Scalable Event Service with Cassandra: Design to Code
tareqabedrabbo
0
73
Time Series and Events: Storage and Querying Strategies with Cassandra
tareqabedrabbo
0
290
Building a Scalable Event Service with Cassandra
tareqabedrabbo
1
130
Other Decks in Technology
See All in Technology
新アイテムをどう使っていくか?みんなであーだこーだ言ってみよう / 20250911-rpi-jam-tokyo
akkiesoft
0
360
Android Audio: Beyond Winning On It
atsushieno
0
3.4k
Apache Spark もくもく会
taka_aki
0
140
Evolución del razonamiento matemático de GPT-4.1 a GPT-5 - Data Aventura Summit 2025 & VSCode DevDays
lauchacarro
0
210
Autonomous Database - Dedicated 技術詳細 / adb-d_technical_detail_jp
oracle4engineer
PRO
4
10k
IoT x エッジAI - リアルタイ ムAI活用のPoCを今すぐ始め る方法 -
niizawat
0
130
LLMを搭載したプロダクトの品質保証の模索と学び
qa
1
1.1k
Create Ruby native extension gem with Go
sue445
0
130
20250910_障害注入から効率的復旧へ_カオスエンジニアリング_生成AIで考えるAWS障害対応.pdf
sh_fk2
3
280
要件定義・デザインフェーズでもAIを活用して、コミュニケーションの密度を高める
kazukihayase
0
120
slog.Handlerのよくある実装ミス
sakiengineer
4
480
人工衛星のファームウェアをRustで書く理由
koba789
15
8.3k
Featured
See All Featured
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
507
140k
Writing Fast Ruby
sferik
628
62k
Why Our Code Smells
bkeepers
PRO
339
57k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
PRO
188
55k
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
53
3k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
52
5.6k
Become a Pro
speakerdeck
PRO
29
5.5k
The Power of CSS Pseudo Elements
geoffreycrofte
77
6k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
12
1.1k
GraphQLとの向き合い方2022年版
quramy
49
14k
Optimizing for Happiness
mojombo
379
70k
Build The Right Thing And Hit Your Dates
maggiecrowley
37
2.9k
Transcript
The 7 Deadly Sins of Microservices Tareq Abedrabbo - MuCon
2014
About me CTO at OpenCredo Author, developer, open-source committer, with
a long term interest in service-based architecture
Disclaimer Any resemblance to existing projects, overrunning or axed, is
purely intentional!
What are microservices?
Microservices Design Principles Tools Decoupling Separation of concerns Encapsulation Engineering
Practices Spring Boot RabbitMQ Hystrix Automation Scalability Fault-tolerance Continuous Delivery Testing Dropwizard Config Management
Why microservices anti-patterns?
1. The Enterprise-OSGI-Application-Service-Bus Building the wrong thing
There is no unique way to implement microservices
Don't build what you don't need - think about your
goals and your non-goals
Questions to ask: - What languages do I need to
support? - What libraries? - How dynamic and flexible does my implementation need to be?
Communicate goals and non-goals. Keep it simple.
2. Porcine Cosmetics Failing to adopt a contract-first design approach
Why do we need service contracts?
Abstraction
Encapsulation
Composition
Always start by designing the contract of your service (CDD,
it is like TDD but for microservices!)
Seriously, we've known this for 10 years!
3. Message in a Bottle Assuming the wrong communication protocol
Typically, microservices use http or lightweight messaging to communicate. Messages
can be binary or human-readable
Don't enforce one particular communication pattern before understanding what you
really need
Do I need: - Simple request/response paradigm? - Message persistence?
- Reliability? - Asynchronous notification?
Distinguish between services: external vs internal core vs supporting
4. The Single Domain of Failure Introducing a shared domain
model
Designing a shared domain model is common in a monolithic
architecture (it is even a best practice!)
Things domain models are used for: - drive business logic
- map business entities to the database - manage input & output
The shared domain model fallacy: we are in full control
of the context and the boundaries of the application
A shared domain model breaks encapsulation and introduces coupling between
services
Shared dependency on volatile binary artefacts makes deployments really hard
Define the domain in terms of service interaction, not service
implementation
Resource-oriented design
5. The Distributed Monolith Defining inappropriate service boundaries
A distributed monolith is an application that externalises its internal
services indiscriminately
Internal application components don't always make good microservices
Internal application services: - often have the wrong granularity -
can have interdependencies - or a dependency on a shared domain
Microservices are not a remoting abstraction
Design services that have business meaning and clear boundaries
6. The Horseless Cart Neglecting Macro System Concerns
Microservices: micro vs macro (macro is often missed)
Macro things to think about: - updating, deploying and scaling
services independently - functional, performance and regression testing - system-wide behaviour, including failure scenarios
Design for a distributed system (runtime introspection, fault-tolerance, latency, failure,
etc...)
Introduce continuous delivery and automated testing form the very start
7. The Sausage Factory Disregarding the Human Factor
In microservices world, developers need to have good understanding of:
- Messaging - Scalability, fault-tolerance and resilience - Integration and remoting And potentially learn a few new technologies and tools
Monolithic architecture is a rabbit hole!
Microservices do not make up for the gaps in your
developers' skills
Invest in your developers
–Melvin Conway “organisations which design systems […] are constrained to
produce designs which are copies of the communication structures of these organisations.”
Corollary organisations that operate in silos cannot benefit from a
microservices architecture
Microservices do not fix broken organisations
Collaboration on a microservices project between: - devs and ops
- techies and business - and across teams
The essence of microservices is collaboration
In conclusion
Microservices: it feels a little bit like quantum mechanics!
Hopefully, we can now begin to have pragmatic answers to
questions such as: - How do I design a (micro)service? - How big or small should a service be? - Should a microservices be reusable?
Links Microservice anti-patterns: http://bit.ly/ microservices-antipatterns OpenCredo: http://www.opencredo.com/blog Twitter: @tareq_abedrabbo Personal
blog: http://www.terminalstate.net Thank you! Any questions?
Credits • https://unsplash.com/ • The horseless cart: https://www.flickr.com/photos/ ellesmerefnc/4249596803/ •
Message in a bottle: https://www.flickr.com/photos/ rpenalozan/5128413528