The distributed monolith
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
spot the worst of both worlds.
Planned topics
- A distributed monolith has separate deployments but cannot change or deploy independently.
- Signs: lockstep releases, shared database, long synchronous call chains, a shared "common" library with domain types.
- It keeps the monolith's coupling and adds network costs.
- Usual causes: boundaries by technical layer or per entity, and shared data.
- Test: can you deploy one service alone, at any time, without breaking another?
Draft outline details
Demonstration
a diagram of four services all reading one shop database, with a release train arrow.
Check your understanding
What is the quick test for a distributed monolith?
Show answer
Cannot deploy one service independently.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.