Avoiding Microservice Megadisasters - Jimmy Bogard
You've spent months re-architecting your monolith into the new microservices vision. Everyone gathers around to flip the switch. You navigate to the first page...and nothing happens. Refresh...still nothing. The site is so slow, it won't respond for minutes. What happened? In this session, I'll walk through a post-mortem of a real-life microservice disaster. I'll show the modeling, development and production problems we found, and how we slowly morphed the new distributed monolith into our final picture of sanity. While we can't prevent project failures, we can at least identify problems early on in our design so that our final product results in a clean, robust distributed system. NDC Conferences https://ndc-london.com https://ndcconferences.com
Chapters
- 0:00 Intro
- 0:46 Bell Computers
- 6:06 Netflix-oriented architecture
- 6:21 Core principles No data duplication
- 11:29 Doing the math
- 13:38 They're called "fallacies"
- 14:52 How Not to Do It (MS Style)
- 17:36 Traditional n-tier
- 17:51 Areas of Responsibility
- 18:53 what is a Service? Software that is...
- 19:52 what is a Microservice?
- 20:18 what is a Bounded Context?
- 24:33 Data ownership
- 26:30 Service Dependency Inversion
- 28:50 Catalog
- 31:00 Pricing
- 33:03 Localization
- 43:05 Avoiding Microservice Megadisasters
- Channel
- NDC Conferences
- Views
- 162