11–20 of 54 posts
They should have chosen name that doesn`t immediately make users want to uninstall it.
Why? Conduit seems as good a name as any for a project like this, if you ask me. Am I missing something here?
It does seem like JVM based products standard answer "Buy More hardware" is becoming untenable.
At first glance, this looks like a direct competitor to Envoy[1]. I'm sure the documentation will improve as the product matures, but right now much is left to the imagination. Could you perhaps go in to more detail on the differences between the two? [1] https://www.envoyproxy.io/
Like Linkerd, Envoy is a proxy that can be used used to build a service mesh. Conduit is a service mesh that includes a proxy. So, yes, Conduit uses something that competes with Envoy ;) But I would not say that Conduit and Envoy are equivalent things.
They should have chosen name that doesn`t immediately make users want to uninstall it.
I love seeing things move from Java/PHP/Ruby to Go (or better) Rust. Memory usage plummets.
But what in the hell is it? If your product is so revolutionary it defines a new market segment, you might want to bring the people with the money people up to speed.
> Conduit's Rust-based data plane proxies run in less than 10mb RSS and have sub-millisecond p99 latencies. I love seeing things move from Java/PHP/Ruby to Go (or better) Rust. Memory usage plummets.
Earlier quoted context omitted.
Why? Conduit seems as good a name as any for a project like this, if you ask me. Am I missing something here?
"Conduit" is often refered to "Conduit toolbar" [1], which was known as a malware. [1]: https://en.wikipedia.org/wiki/Conduit_toolbar