The document discusses the benefits of service meshes like Istio for managing microservices. It describes how microservices introduce operational complexity, network unreliability, and difficulties with observability and security. Service meshes address these issues by adding a sidecar proxy to each microservice container that handles tasks like load balancing, authentication, and monitoring. The sidecar implements features from a control plane configuration while the data plane handles network communication.

1. The personas that benefit from
a Service Mesh
Intro to Service Mesh &
Istio

2. 2 | Copyright © 2022
Field Engineer @ EMEA
Solo.io
Speakers
Rinor Maloku
@rinormaloku
rinor.maloku@solo.io
https://rinormaloku.com
https://www.linkedin.com/in/rinormaloku/

3. 3 | Copyright © 2022
Field Engineer @ APAC
Speakers
Kamesh Sampath
kamesh@solo.io
https://kamesh-sampath.medium.com
https://github.com/kameshsampath
https://linkedin.com/in/kameshsampath
Open Source Contributor for more
than a decade
● Tektoncd
● Knative
● Minikube
● Eclipse Che
● Camel-K
@kamesh_sampath

4. 4 | Copyright © 2022

5. 5 | Copyright © 2022

6. 6 | Copyright © 2022
How we got to service meshes?

7. 7 | Copyright © 2022
Everything started with the big bang

8. 8 | Copyright © 2022
Everything started with the big bang

9. 9 | Copyright © 2022
Benefits of microservices

10. 10 | Copyright © 2022
Which node or
cloud where
the service is
failing
Is our
system
secure?
Why my
service
fails ??

11. 11 | Copyright © 2022
Microservices trade-offs

12. 12 | Copyright © 2022
Microservices trade-offs
Weakness of strength
every strength that an individual a
system has necessarily brings with it a
weakness of which it is an inherent part
– Henry James
“

13. 13 | Copyright © 2022
The inherent weakness of microservices
Microservice Trade-offs https://martinfowler.com/articles/microservice-trade-
offs.html#distribution

14. 14 | Copyright © 2022
Solution to Operational Complexity

15. 15 | Copyright © 2022
Solution to network unreliability
Fallacies of distributed computing:
● The network is reliable
● Latency is zero
● Bandwidth is infinite
● The network is secure
● Topology doesn't change
● There is one administrator
● Transport cost is zero
● The network is homogeneous

16. 16 | Copyright © 2022
Solution to observability

17. 17 | Copyright © 2022
Security is difficult to resolve!
Are we complying with security standards?

18. 18 | Copyright © 2022
Majority of service code is not about business logic

19. 19 | Copyright © 2022

20. 20 | Copyright © 2022

21. 21 | Copyright © 2022
There must be a more effective
solution to the problem!?

22. 22 | Copyright © 2022
There must be a more effective
solution to the problem!?
Service Mesh

23. 23 | Copyright © 2022
How service meshes improve that
Microservices Patterns With Envoy Sidecar Proxy: The series by Christian Posta

24. 24 | Copyright © 2022
How the sidecar implements the features

25. 25 | Copyright © 2022
Data plane and control plane

26. 26 | Copyright © 2022
Data plane and control plane

27. 27 | Copyright © 2022
Demo

28. 28 | Copyright © 2022
Resources
References:
● Code repo: https://github.com/rinormaloku/happy-istio
● Microservice Trade-offs https://martinfowler.com/articles/microservice-trade-offs.html#distribution
● Microservices Patterns With Envoy Sidecar Proxy: The series
https://blog.christianposta.com/microservices/00-microservices-patterns-with-envoy-proxy-series/
Further reading:
● Getting started with Istio (https://istio.io/latest/docs/setup/getting-started/)
● Traffic management custom resources:
○ Gateway (https://istio.io/latest/docs/reference/config/networking/gateway/)
○ VirtualService (https://istio.io/latest/docs/reference/config/networking/virtual-service/)
○ DestinationRule (https://istio.io/latest/docs/reference/config/networking/destination-rule/)
● Security custom resources:
○ PeerAuthentication (https://istio.io/latest/docs/reference/config/security/peer_authentication/)

29. Thank You!