Mastering Chaos - A Netflix Guide to Microservices

I think that one was good: - [LINK] I wasn't able to find any other talk I watched back then or any of the stuff I did read, but I then last time I looked into talks and reading material about this was ~2.5 Years ago and while a lot of new software and tooling was done since then the principles didn't change. Try some of the other GOTO; talks about it if you like listening to talks, they tend to be quite good. This was interesting as far as I remember but not what I was looking for: - [VIDEO]

> This is unavoidable for many companies, since the code bases are far to large for any single person to grasp them all. That's true, but this was the takeaway from the entire article: > "When we remove that feeling of “I need to know how allllll of this works, but just enough so that I can rescue it when it breaks”, we facilitate the mental room to iterate on our team’s systems with greater depth." To me it sounds like they've now introduced exactly that feeling with micro-services, developers now need to know how all services and front-ends work, and how they interact with each other. Maybe the article is poorly structured, but if that's the entire takeaway from moving to micro-services and micro-frontends, then I do question their choice. > Netflix [VIDEO] Netflix is indeed one example. It's hard to argue it doesn't work, but from my experience, it never worked out the way it was envisioned.

Netflix was talking alot about circuit breaks a few years ago, and had the Hystrix project. Looks like Hystrix is discontinued, so I'm not sure if there are good library solutions that are easy to adopt. Overall I don't see it getting talked about that frequently... beyond just exponential backoff inside a retry loop. - [LINK] - [VIDEO] I think talks about Hystrix a bit, but I'm not sure if it's the presentation I'm thinking of from years ago or not.