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
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.
![Kodak Black - Versatile 4 [Official Video]](http://i.ytimg.com/vi/VcP_1Ua__vY/mqdefault.jpg)
![Megan Thee Stallion - Roc Steady (feat. Flo Milli) [Official Video]](http://i.ytimg.com/vi/HozPPyqW0dY/mqdefault.jpg)
This is how a tech presentation should be done! Excellent! Key lesson here is not to use service mesh to hide a bad architecture.
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
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.
Perfect timing! Thanks!
Well done. Thank you.
Nice and concise! But would be nice to have ASM mentioned