Seven years with microservices: a critical review
summary
Company runs about 150+ microservices (approaching 200) across ~15 teams on Azure + Kubernetes, with API gateway and Kafka for integration. Teams split into platform vs product teams: platform provides CI/CD, tooling and shared infra; product teams own development, testing and ops. Early failures come from poor tooling and underestimating team readiness; solution is incremental, business-aligned migrations, observability and lightweight end-to-end smoke tests, and at least one senior advocate per team — this combination proves effective.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:27Microservices replacing monoliths
- 4:57Domain service principles
- 9:32Platform vs product teams
- 13:04What worked well
- 15:51Early mistakes and lessons
- 19:45Balancing priorities
- 24:00Seniority in teams
- 25:49Success factors for adoption
- 26:54Q&A
related talks
01h 01mMicroservices Gone Wrong
01h 18mIn Defense of Microservices
51mBig microservices, small team a painful story
45mBuilding and evolving microservices: lessons from the frontlines
41mThe six obstacles of moving to microservices and how to deal with them
37mKnee Deep in Microservices
47mIt is not just Microservices
55mMigrate your company to microservices: a step by step tutorial