Common Mistakes When Moving to Microservices
summary
The talk lists common mistakes organizations make when migrating to microservices and public clouds, naming Kubernetes, cloud managed services, REST, Kafka and CI/CD pipelines specifically. It covers problems such as focusing only on infrastructure rather than domain architecture, misplacing enterprise architects, ineffective architecture guilds, unrealistic QA/end-to-end testing expectations, managers insisting on deployment sign-off, pipelines imposed without enabling DevOps culture, misuse of Kafka as a simple queue, overreliance on half-baked cloud services versus open-source self-hosting, lack of clear repo/team ownership, and ignoring business pivots, and promises concrete suggestions to address each issue.
AI-written summary · about
chapters (11)
- 0:00Microservices introduction
- 4:46Monolith to microservices
- 10:23Enterprise architects' role
- 16:46Architecture design pitfalls
- 23:08Microservices decision-making
- 29:45Team challenges
- 35:48Command-and-control vs empowerment
- 41:10Testing and deployment
- 47:10Microservices security
- 51:44Cloud vs on-premise costs
- 57:02Summary & Q&A
related talks
55mCommon Mistakes When Moving to Microservices & Cloud
51mBottega IL: Common mistakes when moving to microservices
40m10 tips for failing at microservices
39m10 Tips for failing at microservices
20m3 reasons why micro-services aren't the miracle cure
44mMicroservices, Where Did It All Go Wrong
42mPitfalls of Microservice Architecture
43mHow to Avoid Doing Microservices Completely Wrong