Common Mistakes When Moving to Microservices & Cloud
summary
Covers frequent errors teams make when migrating to microservices and cloud, naming specific issues: missing a realistic architecture process (rigid or absent decisions, poor infra vs domain separation, lack of architecture guild/cooperation), QA assuming full end-to-end testing, management insisting on controlling deployments, developers not doing DevOps, misunderstandings of event-based architecture, improper use of tools like Kafka, overreliance on poor cloud-provider tools, and fault-prone team setups and pivots affecting domain-team alignment. Provides solutions or recommendations for each of these concrete problems.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:05Infrastructure diagrams aren't enough
- 6:08Shared architecture understanding
- 8:33Three architecture approaches
- 14:05Architecture guilds pros and cons
- 20:51Architecture diagrams logic
- 26:27Architecture decision process in guilds
- 31:04Org structure vs code quality
- 33:52Team and architecture alignment
- 37:25Org cultures and architecture
- 40:39Teams deploy to production
- 43:27Testing and monitoring in microservices
- 46:57Production environment security
- 50:52Dependencies and system security
- 51:34Tech progress and system design
- 52:58Microservices aren't magic
related talks
58mCommon Mistakes When Moving to Microservices
51mBottega IL: Common mistakes when moving to microservices
42mPitfalls of Microservice Architecture
43mHow to Avoid Doing Microservices Completely Wrong
40m10 tips for failing at microservices
39m10 Tips for failing at microservices
44mMicroservices, Where Did It All Go Wrong
55mMicroservices, Where Did It All Go Wrong