Главная
Study mode:
on
1
Intro
2
Disclaimer
3
Go full scale polyglot
4
Still successful?
5
Polyglot?
6
The data monolith
7
The event monolith
8
How to deal with shared code?
9
2 months later...again
10
The home grown monolith
11
And at runtime???
12
The meat cloud
13
And the rest of the world?
14
Tickets!
15
a few minutes later
16
A system stable as concrete sounds good
17
The decision monolith
18
Beware developer madness
19
Change management
20
Bonus: works with ops, too
21
The prescriptive cloud
22
One Size Fits All
23
PolyWTF works for ops
24
The staffing monolith
25
Frequent Flyer Program Rail-Bonus Program Hotel Credit Points
26
Dysfunctional setup in 3 easy steps
27
How to do X-team communication?
28
Protect the teams
29
Establish bureaucracy
30
Enter the fakeholder!
31
shadow product owner proxy product owner
32
Technical benefits?
33
Shared release
34
And: In case of bugs...
35
The monolith starts in the head
Description:
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.

Tips for Failing at Microservices

Devoxx
Add to list