InfoQ Homepage Service Mesh Content on InfoQ
-
Securing Cell-Based Architecture in Modern Applications
Securing cell-based architecture is essential to fully capitalize on its benefits while minimizing risks. To achieve this, comprehensive security measures must be put in place. Organizations can start by isolating and containing cells using sandbox environments and strict access control mechanisms like role-based and attribute-based access control.
-
Article Series: Cell-Based Architectures: How to Build Scalable and Resilient Systems
In this article series, we take readers on a journey of discovery and provide a comprehensive overview and in-depth analysis of many key aspects of cell-based architectures, as well as practical advice for applying this approach to existing and new architectures.
-
The Future of Istio: Sidecar-Less and Sidecar with Ambient Mesh
Istio's new ambient mesh allows for a sidecar-less data plane. This article discusses the advantages of that approach and the work that went into making it a reality.
-
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.
-
The What and Why of Programmable Proxies
A question which gets often asked is “What is a programmable proxy, and why do I need one?” This article tries to answer this question from different perspectives. We will start with a brief definition of what a proxy is, then discuss how proxies evolved, explaining what needs they responded to and what benefits they offered at each stage. Finally, we discuss several aspects of programmability.
-
Data Patterns for the Edge: Data Localization, Privacy Laws, and Performance
With growing competition to get data that power experiences to the end-user closer and closer and the advent of local data privacy laws, let's look at different enterprise data patterns like “synchronous data retrieval”, “subsequent data retrieval” and “prefetch data retrieval” on data center.
-
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.
-
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.
-
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.
-
Implementing Microservicilites with Istio
Microservicilities is a list of cross-cutting concerns that a service must implement apart from the business logic. These concerns include invocation, elasticity and resiliency, among others. This article describes how a service mesh such as Istio may be used to implement these concerns.
-
Adoption of Cloud Native Architecture, Part 2: Stabilization Gaps and Anti-Patterns
In this second part of cloud native adoption article series, the authors discuss the anti-patterns to watch out for when using microservices architecture in your applications. They also discuss how to balance between architecture and technology stability by not reinventing the wheel in every new application and at the same time, avoiding arbitrary reuse of technologies.
-
Multi-Runtime Microservices Architecture
Best practices have emerged around “microservice” architecture and “12-factor app” design. As cloud, containers, and container orchestrators (.g. Kubernetes) have become popular, new solutions to address common integration principles have emerged. This article discusses the approach of using "mecha" components to provide enterprise integration pattern functionality for microservices.