
Monolith Is Not an Anti-Pattern

#53 - Principles for Adopting Microservices Successfully - Chris Richardson
Topic 4 of 10
Published Aug 30, 2021 · Clip 15:46–18:59 (3:13)
Chris explains why a monolith is not an anti-pattern: it is simple and familiar, with method calls between modules and a single database supporting ACID transactions. In contrast, microservices involve interprocess communication, private databases per service for loose coupling, which complicates transaction management, forces eventual consistency, and introduces runtime coupling that impacts availability.