HackerTube.dev

Avoiding Microservice Megadisasters - Jimmy Bogard

NDC Conferences · 438.9K views · 2017-04-06 · 45:27

Open on YouTube ↗

If playback is restricted in your region, try opening the original video. Use Mark watched to add it to your marked videos.

Overview

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.

On Hacker News

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

Recommended by 2 HN people across 2 months · HN mentions 2018–2023

Topics

Software architecture & designDistributed systems
Search by tags
microservicesdistributed monolithconway's lawarchitecturepost-mortem

What people said

ketzu · 2023-06 · Recommendation

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

Read the original HN comment ↗
tony-allan · 2018-11 · Recommendation

[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.

Read the original HN comment ↗
etripe · 2020-01 · Reference

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] [VIDEO]

Read the original HN comment ↗

Sources

Video by NDC Conferences, played through YouTube.

Data and selection notes

HN summaries and labels may contain AI errors. HN dates refer to discussions, not video publication.

HN Library: HackerTube export (2026-10-31) and open-index/hacker-news. Upstream summaries and classifications may contain AI errors.

Views, duration and playback status refresh separately from the published catalog. When an update fails, existing data remains visible.

Selection checks
  • SaaS & AI candidates: Topic keywords do not match
  • Editor-approved picks: Editorial review is required

Rule matches identify candidates. They do not guarantee video quality or financial results.

About the library and its sources