Plays with YouTube's privacy-enhanced embed

Avoiding Microservice Megadisasters - Jimmy Bogard

Name: Avoiding Microservice Megadisasters - Jimmy Bogard
Description: Jimmy Bogard presents a post-mortem of a real microservices migration that turned into a slow distributed monolith. He covers the modeling, development and production problems and how the team recovered.

NDC Conferences Talks intermediate

Open on YouTube First HN thread

2 HN users recommended this talk in 2 different months between 2018 and 2023.

2007–2026

2 recommendations 1 citation HackerTube score 2

Recommended as an entertaining cautionary talk on microservice failures and Conway's law.

Jimmy Bogard presents a post-mortem of a real microservices migration that turned into a slow distributed monolith. He covers the modeling, development and production problems and how the team recovered.

Pull quote: “Inverse Conway Maneuver: Design the organization you want, the architecture will follow, kicking and screaming.” (HN, 2018)

Also tagged: microservice architecture failures, microservices, distributed monolith, conway's law, architecture, post-mortem

What Hacker News said

3 labeled comments from the HN archive; up to 20 are kept per video, favoring different commenters. Each one links back to the original thread.

Recommends tony-allan November 2018 under Avoiding Microservice Megadisasters

Conway's law and inverse Conway maneuver at 39:00

[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

Recommends ketzu June 2023 under Make microservices look like monoliths

Entertaining talk on microservice failures

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 ( [this video] )

View on Hacker News

Citations, criticism and jokes

Cites it etripe January 2020 under Reasons for Doing Microfront Ends

Example of a microservices disaster at Bell

Read the full comment

As your average developer who's heard architects mention these micro-frontends, I would have liked the article to start off by listing the use cases and trade-offs instead of jumping right on the hype train at full speed. Since the article mentions Piral, I thought I would peruse that project's documentation (0), but am none the wiser on basic questions like: how do components get assembled into the main application, is network traffic overhead is going to be a problem, etc. Delving further into the Piral docs, I came across a link to a sample micro-frontend (1) that seems to be importing every micro-frontend 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] [this video]

View on Hacker News