Loading content
Istio is a production-ready service mesh that centrally manages communication paths between microservices, offering traffic management, policy enforcement and mTLS security. It collects telemetry for monitoring and tracing while decoupling networking concerns from application code. Commonly used in Kubernetes clusters to govern service-to-service communicati…
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Istio is a service mesh platform that governs communication, security, and observability between microservices.
Istio began in 2017 as a joint project by Google, IBM, and Lyft. It brought the service-mesh concept into an open platform and was later developed as an open-source project.
A control plane distributes policy and configuration. Sidecar or ambient data paths mediate service calls, handling mTLS, routing, and telemetry while application code largely avoids implementing those concerns.
It mediates requests between services.
It distributes rules and observes mesh state.
Services authenticate and encrypt their connections.
Istio standardizes cross-cutting concerns in distributed systems. Added complexity, resource use, debugging, and operations need to fit the cluster.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.