Mastering Chaos - A Netflix Guide to Microservices

InfoQ Dev Summit Boston, a two-day conference of actionable advice from senior software developers hosted by InfoQ, will take place on June 24-25, 2024 Boston, Massachusetts.

Deep-dive into 20+ talks from senior software developers over 2 days with parallel breakout sessions. Clarify your immediate dev priorities and get practical advice to make development decisions easier and less risky.

----------------------------------------------------------------------------------------------------------------
Josh Evans talks about the chaotic and vibrant world of microservices at Netflix. He starts with the basics- the anatomy of a microservice, the challenges around distributed systems, and the benefits. Then he builds on that foundation exploring the cultural, architectural, and operational methods that lead to microservice mastery.

[StingSting]

Can't express how high quality this talk is. Wonder if he was a teacher before!

[sundeepreddythirumuru]

One of the best talks I have seen on building systems of high scale, high availability, failure resilient and agility in undergoing change.

[arthurkeech]

One of the best technical talks I've ever seen.

[PeterMoueza]

A timeline :
12:30 EVcache client
16:05 Hystrix Tests
17:55 combinatorial
23:07 consistency
24:53 multi regions failure
26:20 stateless
27:45 stateful
28:40 cache Squid
30:00 EVCache
39:20 API Gateway
45:00 Actions
45:40 AWSreinvent
48:00 RCP
49:20 Conway's law
52:49 cache caching

[OliFubar]

I am sad I found this 3 years late, I've been developing microservices for the past 3+ years but I still learnt a lot from this. A huge belated thanks to you Josh!

[souvikghosh]

I come back to this video once in a while to remind myself how cool the software engineering can be.

[OrdinaryFemmale]

this beast is *ONLY* working for netflix for the last +20 years, that's pretty amazing! thank you for this video, great presentation!

[tidal]

One of, if not the most comprehensive and analogous talks on the subject with relevant, real world stories from someone who has lived it. Thank you.

[ashimov]

1:51 "how amazing the human body is and how something as simple as an act of breathing or interacting with the world is actually a pretty miraculous thing. And it’s actually an act of bravery to a certain extent. There are so many forces in the world, so many allergens and bacterial infections and various things that can cause problems for us." - watching this on Feb 12, 2021 makes me admire this guy and the company he dedicated part of his miraculous life.

[cardboard]

Speaker: "Breathing is a miraculous act of bravery."
2020: "Challenge accepted."

[ErnstFluttert]

Great talk, which is still relevant in 2020! Especially the practical examples, and the solutions they applied. Loved the analogy with the human body. Thnx Josh!

[Patrickdaawsome]

Note to self: Write down summary starting from the 51:25.

P.S. I watched the whole thing and absolutely loved it.

[sandy.aggarwal]

Watched again 3 years later and it's still so relevant.

[martinmogusu]

This is a really informative talk on microservices, with real challenges and real solutions. The human body analogies make a lot of sense, there's a lot we can learn from nature...

[cthackers]

"The structure of any system designed by an organization is isomorphic to the structure of the organization." Melving E.Conway

[jonopens]

Such a fantastic metaphor to communicate the intent of microservices. As a younger programmer, that really resonated with me.

[markmd]

I just realized that on the globe we have more than 2 millions people that have interest in microservice architecture

[Mike.e]

Excellent talk. Envious of your delivery! Thank you!

[gashinamu]

One of the best tech talks I've ever watched.

[kibizr]

AKA: Obfuscating Chaos - A Netflix Guide to Creating Dysfunctional Organizations

Basically, a dev noticed: Hey, these two components could benefit from having isolated processes.

And a manager said: Wait, could this also be used to stop Team A from complaining about consuming Team B's code?

Thoughtful dev replied: Well, it depends on the specific components... Some components are fundamentally coupled, so they can't survive a partition anyway, and introducing one for the sake of team boundaries will just create more technical problems without solving the underlying social problems.

Manager blinked twice, and after he rebooted he said: But they'll shut up about each others' code?

Dev: I mean, technically. They'll just complain about API contracts instead --

Manager: Perfect.

Dev: -- which is arguably worse, because as soon as you have a multistep process or something involving callbacks or dependency injection, you have a huge mess, and that's even if you can sidestep the CAP theorem for all of your use cases, which is a really big assump--

Manager: Yeah, yeah, whatever. So how soon can we do this?