English
The lecture covers why teams over - split too early. Then, the lecture covers worst case: the distributed monolith Communication, state and resilience.
Next, the lecture covers database per service, shared DB, event sourcing. Then, circuit breakers and failure handling Microservices Architecture A monolith is often the correct first architecture Microservices only win when team structure, deployment maturity and domain complexity justify the extra operational cost.
Next, the lecture covers one team owns the product end to end. Then, the domain is still evolving quickly.
Next, the lecture covers you deploy a few times per day, not hundreds. Then, the codebase becomes hard to navigate.
Next, incidents in one module can block the entire release train. Then, start with a modular monolith when:.
Next, boundaries are not yet stable. Then, platform automation is weak Microservices are expensive to buy before you actually need them.