Tips for Failing at Microservices

Explore 10 humorous yet insightful tips for failing at microservices in this 40-minute conference talk from Devoxx. Learn from real-world experiences in both greenfield and brownfield projects, covering common pitfalls such as ignoring organizational impact, focusing solely on code, and neglecting operations and testing. Discover how to misuse event sourcing, CQRS, and cloud scaling, while adding unnecessary complexity to your projects. Gain valuable insights into the challenges of microservices architecture, including polyglot persistence, shared code management, and runtime issues. Examine the pitfalls of poor change management, dysfunctional team setups, and misaligned organizational structures. By understanding these anti-patterns, develop a deeper appreciation for the complexities of microservices implementation and the importance of holistic system design.

Intro
Disclaimer
Go full scale polyglot
Still successful?
Polyglot?
The data monolith
The event monolith
How to deal with shared code?
2 months later...again
The home grown monolith
And at runtime???
The meat cloud
And the rest of the world?
Tickets!
a few minutes later
A system stable as concrete sounds good
The decision monolith
Beware developer madness
Change management
Bonus: works with ops, too
The prescriptive cloud
One Size Fits All
PolyWTF works for ops
The staffing monolith
Frequent Flyer Program Rail-Bonus Program Hotel Credit Points
Dysfunctional setup in 3 easy steps
How to do X-team communication?
Protect the teams
Establish bureaucracy
Enter the fakeholder!
shadow product owner proxy product owner
Technical benefits?
Shared release
And: In case of bugs...
The monolith starts in the head