Avoiding Microservice Megadisasters - Jimmy Bogard
Why Hacker News recommends it
Recommended as an entertaining cautionary talk on microservice failures and Conway's law.
What it is
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.
Recommended by 2 HN commenters across 2 different months, 2018 to 2023.
What Hacker News said
Recommends tony-allan · 2018-11 · on “Avoiding Microservice Megadisasters”
[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.
Recommends ketzu · 2023-06 · 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 ( [this video] )
Cites etripe · 2020-01 · on “Reasons for Doing Microfront Ends”
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 a