ECSA 2023 - Service Mesh Workshop

Ecsa 2023 - Service Mesh Workshop

Transcript

1. Service Mesh Architectures In Microservices Workshop MAHMUT BEYTORUN ECSA 2023, September 19th ISTANBUL
2. WELCOME • Brief overview of microservices architecture • Importance of service mesh in enhancing microservices communication • Workshop agenda overview
3. Challenges in Microservices 1 Increased complexity in service-to-service communication 2 Monitoring and observability difficulties 3 Managing service discovery and load balancing 4 Security concerns in distributed systems
4. What is Mesh? Why Mesh? • Definition: "A dedicated infrastructure layer for facilitating service-to-service communication" • Components: Data plane and control plane • Key functionalities: Traffic management, security, observability, and policy enforcement
5. Sidecar Concept
6. Microservices + Service Mesh
7. The Service Mesh Architecture
8. Benefits of Service Mesh • Improved observability with metrics and tracing • Enhanced security through mutual TLS and access control • Simplified service discovery and load balancing • Seamless rollout of features with A/B testing and canary releases
9. Popular Service Mesh Technologies • Introduction to Istio, Linkerd, and Envoy • Brief overview of each technology's strengths • Selection criteria based on specific use cases and requirements
10. Linkerd Linkerd is an open source service mesh by Buoyant. Linkerd service mesh, offers a number of features like: • Load Balancing • Circuit Breaking • Retries and Deadlines • Request Routing • It instruments top line service metrics like Request Volume, Success Rates and Latency Distribution.
11. Envoy • Envoy as a sidecar proxy • Role in enhancing communication between microservices • Features: Dynamic configuration, observability, and extensibility
12. Istio • Istio is an open platform sponsored by IBM, Google and Lyft. It supports Traffic Shaping between micro services while providing rich telemetry. • Fine grained control of traffic behavior with routing rules, retires, failover and fault injection • Access Control, Rate Limits and Quota provisioning • At this point, Istio currently supports only Kubernetes. • Data Plane of Envoy Sidecars that mediate all traffic between services • Control Plane whose purpose is to manage and configure proxies to route and enforce traffic policies.
13. Istio Service Mesh
14. Practical Implementation Considerations • Considerations for introducing service mesh in existing microservices applications • Gradual adoption strategies • Monitoring and measuring success metrics
15. Common Challenges and Best Practices • Addressing challenges in service mesh adoption • Best practices for maintaining and scaling service mesh infrastructure • Importance of ongoing education and community involvement
16. Mesh Demo
17. Thank you! Q & A