Service Meshes: Istio, Linkerd - or No Mesh at All? • Hanna Prinz & Eberhard Wolff • GOTO 2021

Подписаться 998 тыс.

Просмотров 10 тыс.

50% 1

This presentation was recorded at GOTOpia Chicago 2021. #GOTOcon #GOTOpia
gotochgo.com
Hanna Prinz - Co-Author of "Service Mesh" & Consultant at INNOQ
Eberhard Wolff - Co-Author of "Service Mesh" & Fellow at INNOQ
ABSTRACT
Service meshes like Istio and Linkerd 2 solve many problems of current microservice applications. They add observability, routing, resilience, and security features as a dedicated infrastructure layer. Communication between applications can be monitored, configured and secured without adding or changing application code.
Sounds too good to be true? Indeed, a service mesh does not come without a price: mental complexity, increased resource consumption, and latency being the main challenges. We will talk about meaningful use cases for service meshes, drawbacks, and differences between the various implementations [...]
TIMECODES
00:00 Intro
01:25 What is a service mesh? What problems does it try to solve?
05:46 Service mesh implementations
10:42 Service mesh features
22:22 Service mesh challenges
26:05 Do You need a service mesh?
29:02 Conclusion
32:21 Outro
Download slides and read the full abstract here:
gotochgo.com/2021/sessions/17...
RECOMMENDED BOOKS
Eberhard Wolff & Hanna Prinz • Service Mesh • leanpub.com/service-mesh-primer
Eberhard Wolff • Microservices Book • microservices-book.com
Eberhard Wolff • Microservices - A Practical Guide • practical-microservices.com
Sam Newman • Monolith to Microservices • amzn.to/2Nml96E
Aaron Rinehart • Security Chaos Engineering • www.verica.io/sce-book
Nora Jones & Casey Rosenthal • Chaos Engineering • www.verica.io/book
Nora Jones & Casey Rosenthal • Chaos Engineering • amzn.to/3hUmuAH
Mikolaj Pawlikowski • Chaos Engineering • amzn.to/2SQ5Olf
Russ Miles • Learning Chaos Engineering • amzn.to/3hCiUe8
Murphy, Beyer, Jones & Petoff • Site Reliability Engineering • amzn.to/2Vg6Mbr
/ gotocon
/ goto-
/ gotoconferences
#ServiceMesh #Microservices #SoftwareArchitecture #HannaPrinz #EberhardWolff #Istio #Linkerd #ChaosEngineering #Programming #ProgrammingLanguages #INNOQ #ServiceMeshArchitecture #Consul #AWSAppMesh #Traefik #Kuma #OpenServiceMesh #NGINX
Looking for a unique learning experience?
Attend the next GOTO conference near you! Get your ticket at gotopia.tech
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
ru-vid.com...

Наука

Опубликовано:

2 авг 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 6

@techw4y 2 года назад

This is how a tech presentation should be done! Excellent! Key lesson here is not to use service mesh to hide a bad architecture.

@fami5714 Год назад

Thanks for sharing your views on Service mesh Someone can easily be dragged into implementing certain architecture approach like service mesh without really investigating whether it is really needed or not Good conclusion on the topic

@codebreatherHQ 2 года назад

Perfect timing! Thanks!

@ashimov1970 2 года назад

Well done. Thank you.

@myth00s 2 года назад

Hi there and thanks for this video, it was very informative. I don't have much experience with service meshes and trying to understand them a bit more. The last 6 minutes sort of re-inforced some of my thoughts during the first part: 1. Why are my internal services talking synchronously to each other so much? 2. Why are my services fine-grained to the extent they need a whole new type of complex infrastructure to monitor and keep up? Are ops of that scale viable and sustainable? 3. Why am I not composing services to enable workflows, throw orchestration / choreography? 4. Is service mesh a solution to a very niche problem (plethora of fine-grained, synchronously communicating services), or is there value in it in scenarios where asynchronous communication is used? None of the above is meant to be a strong opinion as I don't know enough about the subject - just putting the thoughts out there.