Basic Concepts of Service Mesh

Basic Concepts of Service Mesh An architecture diagram generated by Archify. Service A · Without Service Mesh Service A Service B · Without Service Mesh Service B Service C · Without Service Mesh Service C Control Plane · Policy management · With Service Mesh Control Plane Policy management Service A · With Service Mesh › Pod A Service A Sidecar Proxy · With Service Mesh › Pod A Sidecar Proxy Service B · With Service Mesh › Pod B Service B Sidecar Proxy · With Service Mesh › Pod B Sidecar Proxy Service C · With Service Mesh › Pod C Service C Sidecar Proxy · With Service Mesh › Pod C Sidecar Proxy Direct call Direct call mTLS auto encryption mTLS Config distribution Config distribution Without Service Mesh With Service Mesh Pod A Pod B Pod C Legend Service Control Sidecar

Problems without a mesh

  • • Retry logic implemented in each service
  • • Manual encryption setup between services
  • • Inconsistent metrics collection
  • • Difficult traffic control

Benefits with a mesh

  • • Automatic retry and timeout
  • • Automatic mTLS encryption
  • • Unified metrics and tracing
  • • Fine-grained traffic control