Live data from Hacker News

Envoy: 7 months later

eng.lyft.com

1–10 of 48 posts

Re: Envoy: 7 months later

#2
Envoy is an extremely exciting project. I've been following it closely since OSS inception and am thrilled to see the upcoming deep integration with the Kubernetes project. Such a natural and complimentary fit!

With flexibility as both a side car and host proxy network call fabric for polyglot distributed services, I see Envoy as a kind of modern ESB for the reincarnation of SOA we are seeing in the microservices movement. Congrats to the awesome contributors from Lyft/IBM/Google and others!

Re: Envoy: 7 months later

#6
There was a very interesting talk at Google Next in March that described a way in which the Kubernetes open source team is bringing this sidecar architecture to Kub. In fact I think they are working with the Lyft team. The whole talk is interesting but I've added a time offset to skip to the bit where they talk about sidecar/service mesh.

https://www.youtube.com/watch?v=3quCoi5YHz4#t=27m59s

Also, there is https://istio.io/ but it's a placeholder site at the moment.

Re: Envoy: 7 months later

#7
post #3

Are envoy and linkerd comparable? They look like they fill similar niches, but I'm not familiar enough to know what I don't know.

This. Linkerd has been a pretty cool piece of tech. In fact, their rewrite linkerd-tcp is in Rust and is blazingly fast. Also, it works on L4 and can do more stuff than Envoy... though I think that advantage is going to be shortlived.

Linkerd guys have been focusing on building deep integration with k8s (as an ingress or sidecar), but this announcement of Envoy trumps it all.

>"We are excited to announce that we are working in partnership with both Google and IBM to bring Envoy to Kubernetes. Fun fact: there are now more people working on Envoy at Google than there are at Lyft! We have a lot of other things planned with Google that we will be able to share more about in the coming months."

That's a bummer for the amazing guys at Buoyant. I had hoped for linkerd to be the next generation of ingress in k8s.

Envoy is in C++, while linkerd-tcp is in Rust. I wonder how much role did the choice of tooling play in Google's decision to adopt.

Re: Envoy: 7 months later

#9
post #3

Are envoy and linkerd comparable? They look like they fill similar niches, but I'm not familiar enough to know what I don't know.

This. Linkerd has been a pretty cool piece of tech. In fact, their rewrite linkerd-tcp is in Rust and is blazingly fast. Also, it works on L4 and can do more stuff than Envoy... though I think that advantage is going to be shortlived. Linkerd guys have been focusing on building deep integration with k8s (as an ingress or sidecar), but this announcement of Envoy trumps it all. > "We are excited to announce that we are…

Isn't linkerd in Scala and linkerd-tcp a small subset of it?
Post reply on HN