InfoQ Homepage Linkerd Content on InfoQ
Articles
RSS Feed-
/articles/ebpf-service-mesh/en/smallimage/ebpf-service-mesh-small-logo-1665571213645.jpg)
eBPF and the Service Mesh: Don't Dismiss the Sidecar Yet
While eBPF looks promising to improve service mesh sidecar proxy performance, there are other, simplier ways to improve performance. The layer 7 processing needed for service meshes is unlikely to be feasible in eBPF for the foreseeable future, which means that meshes will still need proxies.
-
/articles/service-mesh-unnecessary-complexity/en/smallimage/logo-1632479954476.jpg)
How Unnecessary Complexity Gave the Service Mesh a Bad Name
There is immense value in adopting a service mesh, but it must be done in a lightweight manner to avoid unnecessary complexity. Take a pragmatic approach when implementing a service mesh by aligning with the core features of the technology, such as standardized monitoring and smart routing, and watching out for distractions.
-
/articles/service-mesh-ultimate-guide-2021/en/smallimage/logo-1630968100375.jpg)
Service Mesh Ultimate Guide 2021 - Second Edition: Next Generation Microservices Development
Get up to speed on the adoption of service mesh. Learn how to deploy service mesh solutions in heterogeneous infrastructures and application/service connectivity.
-
/articles/cloud-native-architecture-adoption-part3/en/smallimage/adoption-cloud-native-architecture-part-3-logo-small-1630316844867.jpg)
Adoption of Cloud Native Architecture, Part 3: Service Orchestration and Service Mesh
This part 3 article in Cloud Native Architecture Adoption series, explores service interaction in a microservices based architecture, typical challenges we experience in distributed systems without proper governance, and how patterns like service orchestration and service mesh can help address those challenges.
-
/articles/linkerd-v2-production-adoption/en/smallimage/linkerd-v2-production-adoption-s-1554326459659.jpeg)
Linkerd v2: How Lessons from Production Adoption Resulted in a Rewrite of the Service Mesh
Linkerd 2.0 introduced a substantial rewrite of the widely adopted service mesh, using a split between Go and Rust. In this article, we discuss the lessons learned in the "cauldron of production adoption", and how those lessons became the basis of Linkerd 2.x’s philosophy, design, and implementation.
-
/articles/adopting-new-tech-service-mesh/en/smallimage/adopting-new-tech-service-mesh-logo-1531154551611.jpg)
How to Adopt a New Technology: Advice from Buoyant on Utilising a Service Mesh
When adding a new technology like a service mesh into your production stack, be mindful of the impact this will have on you and your colleagues. Be clear about what problem you are solving, and define appropriate acceptance criteria. Run experiments that attempt to show how a service mesh can make life better for the various stakeholders.