From Microservices to Migroservices
summary
Explains that moving a monolith to microservices can create a “distributed monolith” (called a migroservice) that adds network faults, orchestration and ops cost without reducing business complexity. Discusses concrete technologies—Docker containers, Kubernetes, service discovery, reverse proxies, circuit breakers, message brokers like Kafka and consensus tools (Raft)—and warns against sharing the database; reports projects where deployments slow, accidental complexity and bills grow unless full automation and clear bounded contexts are enforced.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:12Microservices in 2019
- 2:16Monolith problems
- 6:30Microservices promises
- 12:03Migroservices when they fail
- 15:38Microservices not magic
- 21:15Microservice boundaries trap
- 25:46Conway's law
- 27:08Service communication issues
- 33:08Shared database bad
- 35:58Distributed workflows
- 37:43Microservices operational cost
- 40:30Automation keys
- 42:18Monitoring in distributed systems
- 44:46Total automation
- 45:06Microservices not universal
- 48:13Q&A
