Service Mess
to Service Mesh
by Rob Richardson
About Me
Rob Richardson is a software craftsman building web properties in ASP.NET and Node, React and Vue. He's a frequent speaker at conferences, user groups, and community events, and a diligent teacher and student of high quality software development. You can find this and other talks on https://robrich.org/presentations and follow him on twitter at @rob_rich.
A Service Mesh
manages network traffic between services
in a graceful and scalable way.
Service Mesh is the answer to:
"How do I observe, control, or secure communication between microservices?"
Service Mesh
OBSERVEmonitor network |
CONTROLaccess policies |
SECUREmutual TLS |
From Monlithic to Microservices
From North-South to East-West
|
|
The Challenge with API Gateways
Service Mesh:
How Does it Work?
Service Mesh
|
OBSERVE monitor network |
CONTROL access policies |
SECURE mutual TLS |
More Than Just a Proxy
 Network Topology |
 Service Health |
 Logging |
More Than Just a Proxy
 Circuit Breaker |
 A / B Testing |
 Beta Channel |
Dashboards
|
|
Prevent Unexpected Traffic Patterns
Service Meshes
- Istio
- Linkerd
- Consul
- Open Service Mesh
Linkerd
Methodology:Linkerd focuses on simple setup and critical features Add 3rd party components to get additional features |
|
Istio
Methodology:A kitchen sink of features to enable / disable Istio combines third-party components:
|
|
DEMO
Service Mesh
- Linkerd
- Istio
In a Nutshell
 Monitoring, Logging, Service Health |
 Intelligent Routing |
 Network Topology Diagram |
Service Mesh Implementation Cost
|
+ |
|
Benefits of Service Mesh
|
OBSERVE transparency of communication |
CONTROL enhanced resilience to network disruption |
SECURE abstraction without code changes |