English
The lecture covers monolithic vs microservices: pros and cons. then, the lecture covers worst case: distributed monolith Communication, state and resilience.
Next, the lecture covers API Gateway and service mesh (Istio/Envoy). then, the lecture covers database per service, shared DB, event sourcing.
Next, circuit breakers and failure handling Start with a modular monolith when domain is evolving quickly, boundaries are unstable, and platform automation is weak. then, teams move to microservices when coupling, release friction, and uneven scaling become severe.
Next, a small checkout change can force full regression across unrelated modules. then, catalog reads can dominate CPU while entire app scales together.