Avoiding Microservice Megadisasters - Jimmy Bogard on HackerTube: recommended by 2 Hacker News commenters across 2 separate months, 2018–2023.
talk · intermediate · evergreen
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 as an entertaining cautionary talk on microservice failures and Conway's law.
“Inverse Conway Maneuver: Design the organization you want, the architecture will follow, kicking and screaming.”
3 Hacker News comments link this video. Each one links back to its thread.
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 )
in “Make microservices look like monoliths” · View on HN
▶ 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.
in “Avoiding Microservice Megadisasters” · View on HN
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
in “Reasons for Doing Microfront Ends” · View on HN