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
Un monolith microservice ready – Orange Dev Tes...
Search
Arnaud LEMAIRE
October 16, 2018
Programming
8
280
Un monolith microservice ready – Orange Dev Test Days 2018
Arnaud LEMAIRE
October 16, 2018
Tweet
Share
More Decks by Arnaud LEMAIRE
See All by Arnaud LEMAIRE
From Code to Consequences – AlpesCraft 2025
lilobase
0
440
Scaling in Three Dimensions – Data In Motion Paris 2024
lilobase
0
45
Intervention Michelin DORD
lilobase
0
120
The strategies behind ddd – AdeoDevSummit 2022
lilobase
6
1.4k
Let's reset Agile at Scale — Lean&Agile day Michelin 2022
lilobase
2
340
Sunday, retour d’expérience sur la construction d’une entreprise attractive pour les techs – Tech.rocks 2021
lilobase
1
180
Le projet legacy, quelles stratégies pour s'en sortir ? – Software Crafts·wo·manship Rennes juin 2021
lilobase
4
600
Réconcilier architecture logicielle & problématiques métiers : une introduction au Domain Driven Design – Blend Web Mix 2021
lilobase
5
1.1k
La qualité d’aujourd’hui est la productivité de demain — Orange Innovation School mars 2021
lilobase
1
620
Other Decks in Programming
See All in Programming
実用的なGOCACHEPROG実装をするために / golang.tokyo #40
mazrean
1
230
ソフトウェアテスト徹底指南書の紹介
goyoki
1
140
🔨 小さなビルドシステムを作る
momeemt
3
660
UbieのAIパートナーを支えるコンテキストエンジニアリング実践
syucream
2
830
DockerからECSへ 〜 AWSの海に出る前に知っておきたいこと 〜
ota1022
5
1.9k
CloudflareのChat Agent Starter Kitで簡単!AIチャットボット構築
syumai
2
430
Ruby×iOSアプリ開発 ~共に歩んだエコシステムの物語~
temoki
0
250
速いWebフレームワークを作る
yusukebe
5
1.7k
KessokuでDIでもgoroutineを活用する / Go Connect #6
mazrean
0
140
AIエージェント開発、DevOps and LLMOps
ymd65536
1
380
FindyにおけるTakumi活用と脆弱性管理のこれから
rvirus0817
0
430
Go言語での実装を通して学ぶLLMファインチューニングの仕組み / fukuokago22-llm-peft
monochromegane
0
120
Featured
See All Featured
GraphQLの誤解/rethinking-graphql
sonatard
71
11k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
29
1.9k
Java REST API Framework Comparison - PWX 2021
mraible
33
8.8k
[RailsConf 2023] Rails as a piece of cake
palkan
57
5.8k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
23
1.4k
Scaling GitHub
holman
463
140k
Testing 201, or: Great Expectations
jmmastey
45
7.6k
Practical Orchestrator
shlominoach
190
11k
Building a Scalable Design System with Sketch
lauravandoore
462
33k
The World Runs on Bad Software
bkeepers
PRO
70
11k
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
26
3k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
229
22k
Transcript
Monolith Microservices ready™ @Lilobase
Complexity is non-linear Complexity System size
Distributed doghouse
-Simon Brown « If you can’t build a monolith, what
makes you think micro-services are the answer ? »
Monolith Microservices -Alvaro Sanchez
-Melvin Conway « organizations which design systems ... are constrained
to produce designs which are copies of the communication structures of these organizations »
-Simon Brown
-Simon Brown
-Simon Brown 1 2
The problem has never been the monolith, but having a
single coupled model
Multiple models lives in your application Invoice Catalog Payment Product
Product Product This is not the same product
The primary coupling in software architecture is when concepts from
separate contexts are entangled
We usually don’t get our models right on the first
try. This is where having a single code base & deployment unit helps with the requested refactoring
Let’s create some hard boundaries
Domain domain interface concrete implementation of the domain interface technical
collaborator
Service A API Service B
Internal API Service A Service B External API Anti-Corruption Layer
(Belong to the infrastructure)
Facade Parent Injector S1 S2
Facade Parent Injector S1 HTTP connector
« Two micro services and their shared database » -Mathias
Verraes
Messages brokers are also datasources
-Cyrille Dupuydauby « Years of fight against ‘DB as a
MoM’ anti- pattern have finally paid off: I am now fighting against ‘MoM as a DB’ anti-pattern. »
Events are not created equal Invoice Catalog Payment Inventory
What about processes
Event or Command driven ? Agent Acteur
Orchestration or choreography ? Orchestration Choreography
Exemple of an event driven orchestrated pattern : the macdonald’s
pattern Counter Ice Cream Hamburgers Salads New Order —— —— —— New Order —— —— —— New Order —— —— ——
Counter Ice Cream Hamburgers Salads
Counter Ice Cream Hamburgers Salads Each time we receive an
item, we check if the order is complete New Order —— —— ——
A time bomb for the optimists
-Graham Lea « They can be hard to see, and
they can sink your app »
Dependencies, even more chances to get failures
Fault tolerance • Rate-limiter • Automatic retry with exponential backoff
• Response caching • BulkHead pattern • Circuit-breaker • Load Balancing Hystrix, Resilience4j
The micro services iceberg
Distributed transaction
Saga T1 T2 T3
Saga T1 T2 T3 C1 C3
Saga T1 T2 T3 T2 Idempotence
PC PC PC Two phases commits T T T
UI Driven Consistency
-Simon Brown
If you cannot deploy independently your services, you don’t have
a micro-service architecture
Going further • Applying the Saga Pattern • Caitie McCaffrey
• Distributed Transactions: The Icebergs of Microservices • Graham Lea • Application Resilience Engineering & Operations at Netflix • Ben Christensen • arpinum/alexandria-api