3 ms·
> ... service mesh for cloud native applications Need I say more? Paging Alan Kay to tell these folks what the origins of an unnecessary complicated mess looks
by dkarapetyan 9y ago
> ... service mesh for cloud native applications
Need I say more? Paging Alan Kay to tell these folks what the origins of an unnecessary complicated mess looks like.
- moondev 9y agoUnnecessary and complicated for whom? If you don't need circuit breaking, retry windows, metrics, ack/nack and advanced load balancing techniques for your platform then you are not the target market. Nobody is forcing you to use it.
- fernandotakai 9y agoif you have a bunch of thrift servers, linkerd is a must. it really makes handling thrift connections much easier.
- dkarapetyan 9y agoLast I checked all of that was already handled at the TCP level but what do I know. Maybe all of that needs to be reinvented at the application level too just to be extra safe. Everything except the circuit breaking I guess which sounds like something an application should worry about itself instead of offloading to another service. Also don't know what this advanced load balancing business is about. What exactly is wrong with HAProxy? So instead of having composable tools we now have this monster called linkerd. Wishing everyone that needs it in their production systems good luck. I'll be fiddling with my VMs and processes while you guys build "distributed" systems.
- deleted 9y ago[deleted]
- defen 9y agoTo pick one example - TCP will get you automatic retry of sending bytes but it knows nothing about the semantics of the layers built on top of it. If your HTTP request to a backend service fails with a 502 - do you try again on the same server? different server? fail the whole thing that was depending on that HTTP request succeeding? TCP can't answer that question for you because it doesn't even know if you're doing a GET or a POST, or what a 502 means.