الفصل 4
Monoliths and Microservices
Choose service boundaries and deployment models without falling into distributed-monolith traps.
ما ستصبح قادرًا عليه
- Explain the architectural purpose of Traditional Monolith.
- Evaluate trade-offs across Traditional Monolith, Modular Monolith, Microservices.
- 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.
0/2 lessons6 questions29 min - 2
Modular Monolith
One deployable unit with real, enforced internal boundaries: what makes a monolith modular rather than merely large, how modules own their data, and how to keep extraction cheap without paying for distribution.
0/3 lessons6 questions43 min - 3
Microservices
What independent deployability actually costs, the organisational prerequisites nobody lists, and a scored decision method for choosing between a monolith, a modular monolith and services.
0/2 lessons6 questions35 min - 4
Service Boundaries
Choosing where to cut is the decision that determines whether a split succeeds: how to find boundaries from data ownership and change history rather than from entity names.
0/2 lessons6 questions32 min - 5
Distributed Transactions
What you lose the moment state spans two services, why two-phase commit is usually the wrong answer, and the two primitives every distributed write depends on.
0/2 lessons6 questions32 min - 6
Saga Pattern
A business transaction as a sequence of local transactions, each with a compensating action — and an honest account of why compensation is a business design problem rather than an undo button.
0/2 lessons6 questions33 min - 7
Backend for Frontend
One backend per client experience, owned by the team that builds that experience: what it solves that a shared API cannot, how it differs from a gateway, and the duplication it costs.
0/2 lessons6 questions31 min