Monoliths and Microservices
Module 1
Traditional Monolith
One deployable unit, taken seriously: what it genuinely gives you, the failure that gets blamed on it unfairly, and the specific symptoms that mean it is actually running out.
29 min2 lessons
Start moduleWhat you will be able to do
- Separate "monolith" as a deployment model from "big ball of mud" as an internal quality.
- List the properties a single deployable provides that distributed systems must rebuild.
- Identify the real symptoms of a monolith reaching its limits.
- Argue for a monolith to a stakeholder who has been told microservices are required.
- 10 min
01A Monolith Is a Deployment Model, Not a Quality Judgement
One unit built, released and run together. That says nothing about whether the inside is well organised — and confusing the two is the most expensive mistake in this chapter.
- 9 min
02The Symptoms That Actually Mean It Is Running Out
Four signals worth acting on, four that are usually misread, and the cheaper interventions to try before any of them justifies distribution.
Traditional Monolith
6 questions · pass at 75%