envoy

To be honest we've not looked into Citus in any depth. My early impression of it (can't speak for the rest of the team) was that it was mostly aimed at sharding analytics workloads, but parts of the docs (e.g. https://docs.citusdata.com/en/v7.1/admin_guide/cluster_manag...) make it sound like it handles OLTP workloads too. Maybe I've been ignoring it for bad reasons! EDIT: Managing Postgres clusters is something that a lot of people are working on. Thought I'd mention two projects that have me excited right now: - Patroni https://github.com/zalando/patroni - Stolon https://github.com/sorintlab/stolon Stolon's client proxy approach in particular looks interesting, and reminds me of how people are using Envoy (https://github.com/envoyproxy/envoy), albeit as a TCP proxy rather than one that understands and can do fun stuff with the data

why both Envoy and Linkerd are on their page as service mesh Linkerd is written in Scala. There are a class of people who avoid the JVM, sometimes for good reasons. For one, Envoy is more resource-efficient. See https://github.com/envoyproxy/envoy/issues/99.

Interesting tags on Github: https://github.com/envoyproxy/envoy Seems like it's the only cats-over-dogs project so far. But not for long ;)

We at Turbine Labs have been contributing to Envoy recently, and it now builds on MacOS! https://github.com/envoyproxy/envoy/issues/128

Sort of expected being a Google project but Istio [1] is being built using Envoy. Google is involved but Envoy [2] is owned by Lyft and is also using Bazel. 1. https://github.com/istio/istio/blob/master/devel/README.md#s... 2. https://github.com/lyft/envoy/blob/master/DEVELOPER.md

Not a complete comparison, but here's[1] a breakdown of Linkerd vs. Envoy (the L7 proxy that sits at the heart of Istio) [1] https://github.com/lyft/envoy/issues/99

Yes.. as a bay area resident can confirm this. I switched totally to Lyft the past few weeks and have no issues finding a ride promptly. Also all drivers that I met seem to be driving only for Lyft. PS: What convinced me to totally switch was this https://github.com/lyft/envoy, my way of saying thanks for the Lyft team.

Looks interesting except imo the configuration makes it basically unusable. They use jinja2 templated json... and there are hundreds of lines for their "simple" examples. Even the "hello world" type example of proxying to google is a mess https://github.com/lyft/envoy/blob/master/configs/google_com...

Lyft has a tech similar to linkerd called Envoy: https://github.com/lyft/envoy. It is a bit lower level than linkerd (based on APIs rather than already integrated with common services) and written in C++. I'm working on an adapter which should offer a better integration with Kubernetes. The end goal is to have envoy be able to replace our Ingress controllers. Not having to run the JVM on every machine is also nice.