A service mesh facilitates efficient and secure communication between microservices in a distributed architecture. It provides essential features such as service discovery, load balancing, security features, and monitoring. By implementing a service mesh, organizations can reduce the complexity of their infrastructure and improve the maintainability of their…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
A service mesh provides service-to-service communication through a dedicated infrastructure layer.
The term developed around distributed microservices. Projects such as Linkerd made the pattern practical as a proxy-based layer for observability, encryption, and policy, while the CNCF describes it as infrastructure for service-to-service communication.
Imagine a small network assistant beside every service. The assistants handle routing, encryption, and measurement while the application keeps its domain logic.
Communication capabilities live in a separate layer.
Supports routing, security, and observability.
A mesh standardises cross-cutting capabilities across services. Its proxy and operational infrastructure add complexity and latency.
Where this building block is located in the topic model.
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.