[ajkjk]

What? Do you have some reason to think Netflix's architecture is deficient?

[paxys]

Because the top 5 comments on HN always say so, so it must be true.

[ilrwbwrkhv]

Overly complicated with microservices. Can be made 10x simpler.

[LinuxAmbulance]

Sometimes simplicity is not the best goal.

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

[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.

[ilrwbwrkhv]

For Netflix level of complexity. Pornhub has more traffic and serves more customer than Netflix with monolithic PHP and some services.

[kredd]

They require completely different levels of viewing patterns and complexity. It’s such a reductionist take.

[ajkjk]

You know something about their internal architecture and why it was built that way and the tradeoffs involved, I guess?