Microservice 2.0 : Service Mesh
From Monolithic to Microservice: challenges brought up: service discovery, load balance, fault tolerance, dynamic routing, etc.
We use client library to build those extra functionalities but difference languages have different solutions, lack of commonalities.
Solution: Service Mesh
WHAT IS A SERVICE MESH? Link
A service mesh is a dedicated infrastructure layer for handling service-to-service communication. It’s responsible for the reliable delivery of requests through the complex topology of services that comprise a modern, cloud native application. In practice, the service mesh is typically implemented as an array of lightweight network proxies that are deployed alongside application code, without the application needing to be aware.
Istio:
Pilot: traffic management
Citadel: Security Protection
Mixer Policy: Strategy execution
Mixer Telemetry: Monitoring
Why use Istio?
Istio makes it easy to create a network of deployed services with load balancing, service-to-service authentication, monitoring, and more, with few or no code changes in service code. You add Istio support to services by deploying a special sidecar proxy throughout your environment that intercepts all network communication between microservices, then configure and manage Istio using its control plane functionality, which includes:
- Automatic load balancing for HTTP, gRPC, WebSocket, and TCP traffic.
- Fine-grained control of traffic behavior with rich routing rules, retries, failovers, and fault injection.
- A pluggable policy layer and configuration API supporting access controls, rate limits and quotas.
- Automatic metrics, logs, and traces for all traffic within a cluster, including cluster ingress and egress.
- Secure service-to-service communication in a cluster with strong identity-based authentication and authorization.
Istio is designed for extensibility and meets diverse deployment needs.
The Road To Architect 