SERVICE MESH: ARCHITECTURAL PRINCIPLES, PERFORMANCE AND PRACTICAL USE IN MICROSERVICE SYSTEMS

Herald of Kazakh-British technical university, 2026

Full text Open access: Gold Metadata (CSL-JSON)
DOI 10.55452/1998-6688-2026-23-2-276-289
Data confidence 70 medium
How this score is calculated

It is built from checkable properties of the record itself: whether the article has a DOI, how many independent sources confirmed its data, whether the required fields are filled in, and how recent the latest confirmation is. Disagreement between sources and a missing identifier lower it. A value of 80 or above means the record was published without further checking; 60 to 79 means it is published at reduced confidence, with a manual check advisable. A record verified by an editor by hand is never pushed below 90 by a recalculation. This scores our data about the article, not the article itself.

Abstract

This paper examines service mesh technology as a dedicated infrastructure layer for managing interservice communication in microservice systems. The objective of the study is to analyze the architectural principles of network layer construction, estimate performance overhead, and demonstrate practical approaches for operationalization in Kubernetes clusters. It describes a model for separating the control plane and data plane, using the sidecar pattern for transparent traffic routing, implementing mTLS, and automatically collecting telemetry. Based on a literature review and open source documentation, a comparative analysis of three key implementations – Envoy, Istio, and Linkerd – is provided based on functionality, implementation complexity, and resource consumption. A practical example of an Istio configuration is provided, using Gateway, VirtualService, and DestinationRule manifests to manage HTTPS traffic and integrate with the Prometheus – Grafana – Jaeger – Kiali observability stack. It was shown that Service Mesh adds moderate overhead in terms of latency and resource consumption, but provides unified management of security and traffic between microservices. The obtained results allow us to formulate practical recommendations on the feasibility of using Service Mesh in enterprise microservice platforms, depending on the system scale and security requirements.