InfoQ Homepage Service Mesh Content on InfoQ
-
/articles/service-mesh-ultimate-guide/en/smallimage/Service-Mesh-pillar-page-logo-1581414272136.jpg)
Service Mesh Ultimate Guide 2020: Managing Service-to-Service Communications
This online guide aims to answer pertinent questions for software architects and technical leaders, such as: what is a service mesh? Do I need a service mesh? How do I evaluate the different service mesh offerings? In software architecture, a service mesh is a dedicated infrastructure layer for facilitating service-to-service communications between microservices, often using a sidecar proxy.
-
/articles/infoq-2019-retrospective/en/smallimage/infoq-roundup-2019-logo-small-1575310425310.jpg)
InfoQ's 2019, and Software Predictions for 2020
We take a look back at what we saw on InfoQ in 2019, and think about what the next year might bring.
-
/articles/cloud-native-architecture-adoption-part1/en/smallimage/adoption-cloud-native-architecture-part-1-logo-1574756652648.jpg)
Adoption of Cloud-Native Architecture, Part 1: Architecture Evolution and Maturity
In this article, authors Srini Penchikala and Marcio Esteves discuss what organizations should assess when adopting cloud native architectures for hosting their applications on cloud. It focuses on architecture hosting models. They also discuss how architecture patterns like microservices, containers, serverless, and service mesh can help with organizational adoption of cloud native solutions.
-
/articles/service-mesh-api-federating/en/smallimage/service-mesh-api-federating-s-1558080393545.jpeg)
Towards a Unified, Standard API for Consolidating Service Meshes
Service mesh architectures enable a control and observability loop. At the moment, service mesh implementations vary in regard to API and technology, and this shows no signs of slowing down. Building on top of volatile APIs can be hazardous. Here we suggest to use a simplified, workflow-friendly API to shield organization platform code from specific service-mesh implementation details.
-
/articles/application-integration-service-mesh/en/smallimage/role-application-integration-cloud-native-microservices-landscape-logo-small-1557478517420.jpg)
Application Integration for Microservices Architectures: A Service Mesh Is Not an ESB
A service mesh is only meant to be used as infrastructure for communication between services, and developers should not be building any business logic inside the service mesh. Other frameworks and libraries can be used to implement cloud native enterprise application integration patterns.
-
/articles/service-mesh-event-driven-messaging/en/smallimage/using-service-mesh-for-event-driven-messaging-logo-small-1557145841741.jpg)
The Potential for Using a Service Mesh for Event-Driven Messaging
In this article, we discuss one of the most challenging and unexplored areas in service mesh architecture; supporting event-driven messaging. There are two main architectural patterns that we discuss here: the protocol proxy sidecar, and the HTTP bridge sidecar. Regardless of the pattern that is used, the sidecar can facilitate features such as observability, throttling, tracing etc.
-
/articles/api-gateway-service-mesh-app-modernisation/en/smallimage/api-gateway-service-mesh-app-modernisation-s-1556793369643.jpeg)
API Gateways and Service Meshes: Opening the Door to Application Modernisation
Modernising applications by decoupling them from the underlying infrastructure on which they are running can enable innovation, reduce costs, and improve security. An API Gateway can decouple applications from external consumers, and a service mesh decouples applications from internal consumers.
-
/articles/kubernetes-multicluster-comms/en/smallimage/kubernetes-multicluster-comms-s-1555590645353.jpeg)
To Multicluster, or Not to Multicluster: Inter-Cluster Communication Using a Service Mesh
Communication within Kubernetes clusters is a solved issue, but communication across clusters requires more design and operational overhead. Before deciding on whether to implement multicluster support, you should understand your communication use case.
-
/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/devops-cloud-trends-2019/en/smallimage/devops-cloud-trends-2019-s-1550778123254.jpeg)
DevOps and Cloud InfoQ Trends Report - February 2019
An overview of how the “cloud computing” and DevOps space is evolving in 2019 including updates on Kubernetes, Chaos Engineering, Service meshes and more.
-
/articles/ambassador-api-gateway-kubernetes/en/smallimage/ambassador-api-gateway-kubernetes-s-1549375314797.jpeg)
Ambassador: Building a Control Plane for an Envoy-Powered API Gateway on Kubernetes
This article provides an insight into the creation of the Ambassador open source API gateway for Kubernetes, and discusses the technical challenges and lessons learned from building a developer-focused control plane for managing ingress or "edge" traffic within microservice-based applications.
-
/articles/istio-service-mesh-tutorial/en/smallimage/istio-service-mesh-tutoriaL-S-1542489920616.jpeg)
Getting Started with Istio Service Mesh Routing
In the following tutorial, we will use Istio to demonstrate one of the most powerful features of service meshes: “per request routing.” This feature allows the routing of arbitrary requests that are marked by selected HTTP headers to specific targets, which is possible only with a (OSI) layer 7 proxy. No layer 4 load balancer or proxy can achieve this functionality.