[miked85]

It's not guaranteed, but much fewer points of failure.

[chipdart]

> It's not guaranteed, but much fewer points of failure.

Can you explain where this is relevant to buffering issues?

Also, you are very wrong regarding failure modes. The larger the service, the more failure modes it has. Moreover, in monoliths if a failure mode can take down/degrade the whole service, all other features are taken down/degraded. Is having a single failure mode that brings down the whole service what you call fewer points of failure?

[miked85]

I can't, since I don't know Netflix's architecture - I was responding to "I'd love to hear exactly how a monolith application is guaranteed to perform better, with details."

[chipdart]

> I was responding to "I'd love to hear exactly how a monolith application is guaranteed to perform better, with details."

I asked nothing about Netflix. My question was directed at your remark regarding monoliths vs microservices.

Now, can you answer the question?

[miked85]

Monoliths might be better in some cases, microservices in others. Performance can obviously differ based on implementation.