Skip to content
Hallway
0:00 / 0:00

#microservices#conway'slaw#distributedmonolith

Avoiding Microservice Megadisasters - Jimmy Bogard

NDC Conferences

230K subscribers • 110 videos on Hallway • Conference channel

YouTube
  • Recommended by 3 people: 2 on Hacker News and 1 on Lobsters.
  • A classic. People kept recommending it from 2018 to 2023.
  • Presented by Jimmy Bogard
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

438K views9 years ago3 recommendations

Software designDistributed systemsMicroservices and monolithsSoftware architectureDesign patterns

Jimmy Bogard presents a post-mortem of a failed microservices migration, explaining how it became a slow distributed monolith and how to fix it.

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 ndc-london.com ndcconferences.com

Why it's here

3 people recommend this

What people say. Recommended as an entertaining and educational post-mortem on the pitfalls of microservice migrations and Conway's law.

tony-allanon Hacker News • Recommends

On “Avoiding Microservice Megadisasters”

link to this video (39:00) Conway's law: Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure. Jimmy's law: A broken, dysfunctional organization driven by meeting unhealthy goals and metrics will produce broken, dysfunctional systems. Inverse Conway Maneuver: Design the organization you want, the architecture will follow, kicking and screaming.
View on Hacker News

ketzuon Hacker News • Recommends

On “Make microservices look like monoliths”

It is such a weird feeling to come across a topic I haven't read on in a while, watch two videos on it out of random curiosity, hop on hackernews the next day, and get a recommendation for the exact same videos. I very much enjoyed the 5 techniques and many of the tidbits. I also liked "Avoiding Microservice Megadisasters" but mostly for the entertainment value ( link to this video )
View on Hacker News

indigoon Lobsters • Recommends

Avoiding Microservice Megadisasters (2017)
1View on Lobsters

u/joeyroguesin r/softwarearchitecture • Mentions

On “Bad architecture design failure examples”

My answer might be a little bit off but interesting nonetheless: link to this video
7View on Reddit

u/paulczyin r/dotnet • Mentions

On “API Gateway using .NET Core, Ocelot and Consul”

Jimmy Bogard has presented several talks on this subject. [video A definite watch before you go off and architect your next project if you must jump on the microservice bandwagon.
7View on Reddit

etripeon Hacker News • Mentions

On “Reasons for Doing Microfront Ends”

…into the index, so network traffic overhead seems like it could be an issue. Does anyone here have experience with these in a production environment and know how to avoid (in my mind) basic pitfalls like these? As it stands, this article seems to be setting people up for scenarios like the Bell micro-services disaster (2) 0 link 1 link 2 link to this video…
View on Hacker News

u/avedeiin r/softwarearchitecture • Mentions

On “Bad architecture design failure examples”

Sounds like Bell?:)) link to this video
2View on Reddit

u/broken-neuronsin r/dotnet • Mentions

On “Why do we need a message broker to communicate between microservices???”

TLDR: Fault tolerance in distributed decoupled service architectures. Microservices regularly fail (and are designed to do so) especially in environments like k8s. It’s also asynchronous so avoids strong coupling. See Six Little Lines of Fail. And Avoiding Microservice Disasters. Both great presentations by Jimmy Bogard.
2View on Reddit

u/desnowcatin r/dotnet • Mentions

On “Oque fazer quando um microserviço precisa de dados do outro?”

You end up with this story if you’re not very very careful. Well worth the watch. link to this video
2View on Reddit