Bottega IL: Common mistakes when moving to microservices
summary
Companies move to microservices by focusing on k8s and cloud rather than domain boundaries and end up with ill‑fitting org roles and brittle systems. A cross‑team Architecture Guild is organized with a rotating chair, a public repo of architecture decision records and PR review templates, pushing teams to own single codebases, per‑service monitoring and separate deployment clusters. End‑to‑end tests prove infeasible so the workflow favors contract tests, focused integration tests, canaries and observability. Also watch for SaaS gaps — missing metrics and hidden failures.
AI-written summary · about
chapters (11)
- 0:00Introduction to microservices mistakes
- 3:46Architecture definition and pitfalls
- 8:14Infrastructure and team decisions
- 13:56Enterprise architect roles and challenges
- 19:12Team autonomy and collaboration
- 24:49Decision-making and consequences
- 30:46Architecture reviews and feedback
- 36:50Team independence and ownership
- 42:30Testing and production deployment
- 48:11Cloud provider and platform choices
- 50:35Summary and closing remarks
related talks
58mCommon Mistakes When Moving to Microservices
55mCommon Mistakes When Moving to Microservices & Cloud
55mMicroservices, Where Did It All Go Wrong
48mIT Architecture : All your micro-services are wrong PERIOD!
39m10 Tips for failing at microservices
52mWhat Does a Good Microservice Architecture Look Like?
44mMicroservices, Where Did It All Go Wrong
43mHow to Avoid Doing Microservices Completely Wrong