Case Studies

All our observability gaps were closed, ...we saw a reduction in failed requests, and experienced cost reduction due to better performance.

Our new deployment process minimized friction and decreased cycle time, which is business-critical. After all, we are a tech company and we must move at a tech-industry pace.

We have offloaded the time and effort needed to develop and maintain the in-house mTLS solution, saving valuable engineering hours.

So, and after yet another “Oh… This problem was caused by Istio!”-moment, we decided the time was ripe to consider the alternatives out there.

[Linkerd] started as our cloud migration tool and ended up being our service mesh of choice.

[Linkerd] worked a little too well to the point of being suspicious. But we liked what we saw and pressed forward with the POC going so smoothly

With Linkerd, we get a lot of capabilities with a lot less complexity. mTLS and free retries are great, but the real benefit we got, was observability. 

Unlike other service meshes that crowd half baked features into the mix, or over-complicated topology choices, Linkerd follows the Unix model of doing one thing well.

Kubernetes allows us to run anywhere, Linkerd enables us to seamlessly connect our clusters, and GitOps provides an audited way to manage our environments.

It was a huge undertaking — especially considering our tight deadline of five months! To our surprise, the mTLS aspect was fairly easy

We started with Linkerd and it turned out to be so easy to get started that we gave up on evaluating the other two — we loved it from the get-go

Because of Linkerd, we’ve been able to easily increase the platform capacity by over 10x, reduce operating costs, and better hit our availability targets

We desperately needed insights into what was happening in the cluster and the new microservices architecture. Without the observability that Linkerd gave us

We have been very happy with the results of installing Linkerd. It alleviates a lot of headaches and takes a minimal amount of management time

The Linkerd service mesh is such an integral part of our environment that I can’t imagine how we’d operate without it. With a small team, we are managing about 2,000 sidecar

As soon as we started experimenting with Linkerd in our non-production clusters, network faults caused by the underpinning Azure instabilities dropped significantly

We rely on Linkerd to help keep customer PPI confidential. If you want TLS, Linkerd takes care of it within the cluster automatically

With the real-time nature of our platform, low latency is a critical factor for us. Linkerd helps our team do rapid triage

One day later we meshed a few services on our test cluster. Two weeks later we meshed [our] first production deployments.