[lcnPylGDnU4H9OF]

> Redundancy, scalability, decoupling, resilience, best possible handling of errors, cost optimization, etc. may be more important at the scale Netflix operates at.

So much that they built a tool to intentionally make things difficult (read: it arbitrarily stops production system processes/containers/etc.) and help inform what decisions to make in favor of fault tolerance.

> Exposing engineers to failures more frequently incentivizes them to build resilient services.

https://github.com/Netflix/chaosmonkey

https://en.wikipedia.org/wiki/Chaos_engineering

[renewiltord]

Embarrassing. I built 99% of Netflix functionality locally with VLC and a subdirectory of mkv files.

[trashburger]

Good for you. Now please aim 10,000 requests a second at your file server.

[renewiltord]

Because I don't use microservices, I don't need 10,000 requests a second to play a video file.

[achierius]

I think the point was 10,000 files on 10,000 different hosts, per second.

[renewiltord]

Well, if they’re only watching one second of video that’s easy. The files could be super small too.

Okay, I can’t keep this up. I was parodying the position not being serious.