Conduit 0.5.0 and the future of Conduit

&gt;Conduit will become Linkerd 2<p>I have not been following this space, is anybody willing to provide background?<p>It looks like linkerd developers re-wrote their Scala service in Rust, citing smaller footprint and lower p99 latency as wins from this approach. As a JVM-hater myself, I fully believe this conclusion, but my mind is open to change. Certainly there&#x27;s at least some nuance? Furthermore, to my knowledge the Netflix plumbing model puts the middleware as java libraries rather than java services, avoiding going through another JVM like Linkerd does. Are stacks like Java and Ruby sufficiently poorly suited for middleware services that developers should be rewriting-in-rust away from them?

Wow, on a side note, when I saw it I almost thought it was the scammy Israel company that used to thrust adware&#x2F;malware through its toolbars back then.<p>[1] <a href="http:&#x2F;&#x2F;malware.wikia.com&#x2F;wiki&#x2F;Conduit_Search" rel="nofollow">http:&#x2F;&#x2F;malware.wikia.com&#x2F;wiki&#x2F;Conduit_Search</a>

One of the biggest draws of Linkerd over Envoy (prior to Consul Connect at least) was that it seemed more feasible to use outside of Kubernetes.<p>Conduit however is tightly coupled to Kubernetes as I understand, which isn’t really addressed in this blog post.