Embracing Microservices
summary
Six recurring failure modes and concrete fixes: projects obsess over tiny service counts instead of starting with a Majestic monolith and splitting only when team friction or scaling pain appears; split gradually (two or three services at a time) and align teams with services; prefer repo-per-service or strict tooling to avoid monorepo bad habits; use CDC or a transactional outbox to avoid lost events when switching to async; embrace eventual consistency and design for at-least-once delivery and idempotency; avoid big shared libraries and uncontrolled tech-zoo proliferation.
AI-written summary · about
chapters (13)
- 0:00Introduction to microservices
- 3:47The myth of microservice size
- 10:17Core idea of microservices
- 13:24When to split into microservices
- 18:28Majestic monolith approach
- 19:53New mindset for microservices
- 23:04Testing in microservices
- 27:21Synchronous vs asynchronous
- 31:16Eventual consistency pitfalls
- 36:33Technology stack diversity
- 39:48Shared libraries and DRY
- 46:13Key takeaways and summary
- 48:47Q&A session
related talks
47mEmbracing Microservices
57mEmbracing Microservices
40m10 tips for failing at microservices
39m10 Tips for failing at microservices
30mHow to Fail at Building Modern Microservices
43mHow to Avoid Doing Microservices Completely Wrong
50mEmbracing Microservices
01h 00mMicroservices, Where Did It All Go Wrong?