> A request to a proxy, which requests to another proxy, which requests to service B?
I hesitate to tell you how many layers are between me an HN's servers right now.
I hesitate to tell you how many layers are between me an HN's servers right now.
How much traffic would be generated if, for every request to HN, six other requests fire? And every time you comment a cascade of requests fire in HNs imaginary K8s cluster?
It’s not that there is anything wrong with this, or that the tradeoff isn’t worth it… it’s just so much data flying back and forth over the wire.
Microservice architecture means there's lot of data flying around, but it keeps local resource utilization predictable.
A mesh doesn't add any extra data back and forth over a wire.
It adds some data being copied from one place in RAM to another place in RAM.