News for hackers. Stuff that matters.
Re:Envoy: 7 months later by moondev on Tuesday April 25, 2017 @12:49PM (#14195407)
Interesting that it seems like there is a bunch of overlap with linkerd in the k8s space. With both k8s and linkerd being CNCF projects, I wonder why google is putting so many resources behind envoy rather than linkerd. I guess that's the beauty of the k8s ecosystem though, freedom and choice to use what you see fit. K8s just provides the rock-solid primitives.
Re:Envoy: 7 months later by politician on Tuesday April 25, 2017 @02:58PM (#14196881)
linkerd has a dependency on the JVM, k8s doesn't, and not everyone wants to pull in the JVM if they're not already using it.
Re:Envoy: 7 months later by Spiritus on Tuesday April 25, 2017 @04:10PM (#14197521)
I guess that's one the reasons they created https://github.com/linkerd/linkerd-tcp
Re:Envoy: 7 months later by lobster_johnson on Tuesday April 25, 2017 @09:42PM (#14199856)
One downside to using Linkerd is that unless you have very few apps — or an overabundance of RAM — you can't realistically deploy it as a "sidecar container". The JVM consumes about 100MB of RAM, by their account; it's not lightweight.

The sidecar pattern (used by Envoy and by Google's new project, istio) is desirable in that it compartmentalizes the rules and logic in the pod that uses them, as opposed to sharing all settings across all apps. Zero dependencies (between pods) is a great way to manage complexity. I haven't thought much about it, but there might be latency benefits, too.