Re:Connecting Kubernetes services with linkerd
by jimktrains2 on Monday April 10, 2017 @10:18PM
(#14084354)
> Why does that require eating bandwidth? It's a proxy. It can derive statistics from past and current connections and make decisions based on that data for new ones without talking to anyone else.
Wouldn't those stats get out of date really quickly if you're not constantly talking to that machine?
> For many a component like this means it's 10 less things to deal with and more time to focus on building features that'll matter to their end users.
But now you have a new component that you need to test and get to know. You didn't get rid of those 10 things, you just compartmentalized them in something else that needs to be maintained.
> Besides, just because it can already be solved doesn't mean it's not worth trying out other approaches.
Very true, I just don't see the particular advantages to using more basic and well-known tools like DNS and TLS.
> Sounds like it requires a lot of cross-talk on my network, eating up bandwidth. That doesn't sound lightweight.
Why does that require eating bandwidth? It's a proxy. It can derive statistics from past and current connections and make decisions based on that data for new ones without talking to anyone else.
> Maybe I'm just an old fogie, or being dense, but I still don't see how this solves any problems I can't and aren't already solving.
So? If you're happy with your solution, keep it! But maybe others haven't solved all these problems, or don't like your approach to how you've solved them for other reasons or don't even want to spend time solving these problems in the first place. For many a component like this means it's 10 less things to deal with and more time to focus on building features that'll matter to their end users.
Besides, just because it can already be solved doesn't mean it's not worth trying out other approaches.