Avoiding Microservice Megadisasters

Explore a post-mortem analysis of a real-life microservice disaster in this conference talk. Delve into the modeling, development, and production problems encountered during a monolith-to-microservices transition. Learn how to identify design issues early on and transform a distributed monolith into a clean, robust distributed system. Discover core principles of microservice architecture, including data ownership, service dependency inversion, and the concept of bounded contexts. Examine common pitfalls in microservice implementation, such as traditional n-tier approaches and misunderstandings about service responsibilities. Gain insights into proper data management, scaling considerations, and the importance of understanding distributed computing fallacies. By the end of this talk, acquire valuable knowledge to avoid microservice megadisasters and create more effective, scalable distributed systems.

Intro
Bell Computers
Netflix-oriented architecture
Core principles No data duplication
Doing the math
They're called "fallacies"
How Not to Do It (MS Style)
Traditional n-tier
Areas of Responsibility
what is a Service? Software that is...
what is a Microservice?
what is a Bounded Context?
Data ownership
Service Dependency Inversion
Catalog
Pricing
Localization
Avoiding Microservice Megadisasters