I have not been following this space, is anybody willing to provide background?
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'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?
Looking forward to Linkerd2
I see a service mesh more as extending the network functionality of the host OS and cluster than the app, which arguably makes rolling it out across a large disparate organisation more feasible.
Conduit however is tightly coupled to Kubernetes as I understand, which isn’t really addressed in this blog post.
And Swarm has been a clear loser for a while now.
I say this despite us running a reasonably sized Aurora/Mesos deployment! Three years ago this was probably the right choice. Today I think you end up debating things like whether or not you should go with self-hosting Kubernetes vs managed vs what Mesosphere is pitching now.