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
17
Scaling in Three Dimensions – Data In Motion Paris 2024
lilobase
0
39
Intervention Michelin DORD
lilobase
0
110
The strategies behind ddd – AdeoDevSummit 2022
lilobase
6
1.4k
Let's reset Agile at Scale — Lean&Agile day Michelin 2022
lilobase
2
330
Sunday, retour d’expérience sur la construction d’une entreprise attractive pour les techs – Tech.rocks 2021
lilobase
1
170
Le projet legacy, quelles stratégies pour s'en sortir ? – Software Crafts·wo·manship Rennes juin 2021
lilobase
4
590
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
610
Other Decks in Programming
See All in Programming
[初登壇@jAZUG]アプリ開発者が気になるGoogleCloud/Azure+wasm/wasi
asaringo
0
130
AIエージェントはこう育てる - GitHub Copilot Agentとチームの共進化サイクル
koboriakira
0
350
データの民主化を支える、透明性のあるデータ利活用への挑戦 2025-06-25 Database Engineering Meetup#7
y_ken
0
320
AWS CDKの推しポイント 〜CloudFormationと比較してみた〜
akihisaikeda
3
310
A2A プロトコルを試してみる
azukiazusa1
2
1.1k
datadog dash 2025 LLM observability for reliability and stability
ivry_presentationmaterials
0
110
PHPでWebSocketサーバーを実装しよう2025
kubotak
0
110
Gleamという選択肢
comamoca
6
760
GitHub Copilot and GitHub Codespaces Hands-on
ymd65536
1
120
iOSアプリ開発で 関数型プログラミングを実現する The Composable Architectureの紹介
yimajo
2
210
PostgreSQLのRow Level SecurityをPHPのORMで扱う Eloquent vs Doctrine #phpcon #track2
77web
2
300
「ElixirでIoT!!」のこれまでとこれから
takasehideki
0
370
Featured
See All Featured
Being A Developer After 40
akosma
90
590k
jQuery: Nuts, Bolts and Bling
dougneiner
63
7.8k
Why Our Code Smells
bkeepers
PRO
337
57k
Build The Right Thing And Hit Your Dates
maggiecrowley
36
2.8k
Designing Experiences People Love
moore
142
24k
It's Worth the Effort
3n
185
28k
Site-Speed That Sticks
csswizardry
10
660
The Invisible Side of Design
smashingmag
299
51k
A Tale of Four Properties
chriscoyier
160
23k
Writing Fast Ruby
sferik
628
61k
For a Future-Friendly Web
brad_frost
179
9.8k
Put a Button on it: Removing Barriers to Going Fast.
kastner
60
3.9k
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