This is literally gold, Now I understand how to learn something 1) knowing what are the problems a tech tool can solve 2) understanding why we use X tool 3) Apply your learnings This is what I take from this video, thanks a ton
You are a genius man, few days back i was wondering that this guy needs to create a video on service mesh , & i got the surprise. ThanKs man, keep doing good work ✌🏼
I don't know how to thank you, You helped me a lot in understanding the service mesh technology. You are doing a great job.Please continue doing. I would like you should bring all new things developed around kubernetes.
7.5k subscribers!! Waw!! You are doing absolutely great! Very informative service mesh video. Waiting for the future servicemesh videos too. Please include Kiali network view component in those if possible. Great job!
the traffic lane analogy for explaining the metrics of requests sent by service A and received by service B was awesome.. only that in the visual, A was receiving because traffic was incoming and B was sending cos traffic was going away :D
"If you can't explain it simply, you don't understand it well enough." -Albert Einstein, And you Sir, You know your stuff! Love your videos, They just hit the nail on t he head.
Mate when you do port forward to playlist api to port 81 locally how does my browser understand it .. I mean you refreshed localhost in the url and it got the content.. same when you deployed db then you didn’t port fwd it but still you refreshed it and got the videos .. how this works ? Sorry if it’s a stupid question
In the first part of the video I used docker compose, no port forwarding, so all services start and the content is there, that is why you can see it all. Later in the video we deploy each service, starting with videos web, at that stage, port--forward does not show any content, we deploy the next service and piece by piece you will notice content coming through in the browser.
Just awesome! But I have one question. If you have your Kubernete cluster on DigitalOcean inside one VPC network, which means that communication between pods is already secure. So what would be the use case for service mesh with TLS connection between pods?
Thank you 💪🏽 TLS between pods means the traffic is encrypted end to end. If your network is comprised, it would be increasingly difficult to sniff packets on the network.
Many kubernetes cluster contain different Environment (prod, stage, Dev), different projects or multiple tenants, so it better to secure the communication.
How do you maintain referential integrity between the videos and playlist databases? Can you do a video on microservice architecture and SQL databases to explain how monolithic apps can be broken into microservices when they all use the same SQL database?
Ideally in world of distributed systems, services should not leak their data model and instead provide a contract thats backward compatible. In this case, playlists-api should not know how videos are stored by the videos-api. Only way to access the data is through the videos-api. The videos-api is able to change its backing service from MySQL to Redis without impacting dependent services as the contract on videos-api (accepting an ID on a GET request) remains consistent. So the videos domain is controlled by its endpoint and no other services should be able to access its database directly. I would recommend to try avoid sharing databases between services as its an anti pattern. 12 Factor is a great read on this 12factor.net/backing-services Microservice video series sounds like a good plan 💪🏽
In Internet there are a lot of documents about velero. Depends on your configuration /setup for concerning solution EG medium.com/techlogs/using-velero-and-restic-to-backup-kubernetes-2f0f812da4db
Personally I would start with Linkerd, then Istio, then also checkout Open Service Mesh. Linkerd is the most beginner friendly mesh out there and you can play around with all its functionality locally using a local kind cluster. It will help you understand all the functionality of a mesh. Istio is slightly more advanced to understand, but once you've played with Linkerd, Istio becomes a real breeze. You don't have to go too advance with Istio, just play with the basics. And finally, Open Service Mesh, will teach you the SMI concepts which may form the foundation of service mesh implementations on Kubernetes going forward. Linkerd ua-cam.com/video/Hc-XFPHDDk4/v-deo.html Istio: ua-cam.com/video/KUHzxTCe5Uc/v-deo.html Open Service Mesh : (video on the roadmap)
Thanks 💪🏽I would highly recommend not to keep sessions in processes (pods), instead move session out (to something like a database). Processes should allow for concurrency (scale out) and share nothing among them. a great read about it here 12factor.net/processes
Thanks for your awesome videos.... Looking forward for more videos on ServiceMesh. My question is how does videos-web container integrated with videos-api & playlists-api? How does Videos-web know about Videos-api/playlist-api?
In this simple demo, videos web runs as a web app (html). It has the URL of playlist api and accesses it via GET call. Videos Api is private and Playlists API is accessing videos API using a GET call over private DNS. This will evolve and an Ingress gateway will be introduced. See full docs here github.com/marcel-dempers/docker-development-youtube-series/blob/master/kubernetes/servicemesh/readme.md
Thanks a lot for the great content man, slightly off topic but there's been some buzz in 2020 regarding Container Operating Systems (BottleRocket, FlatcarLinux, Fedora CoreOS etc..). Is this topic in your rader ?
It's very different. NewRelic integrates at code level (SDK) so it gives deep observability into method\function tracing and instrumentation. NewRelic would compare more to Prometheus + Jaeger to a degree. Service mesh gives you more network level tracing focusing on endpoints. I.E When service A calls B, B's endpoint took 5ms to respond, but it does not instrument the code of endpoint B which is what NewRelic would do if that makes sense 💪🏽
Best video I viewed so far on Service Mesh introduction.
Likewise
The most perfect explanation of Service Mesh concept ever
This is literally gold, Now I understand how to learn something
1) knowing what are the problems a tech tool can solve
2) understanding why we use X tool
3) Apply your learnings
This is what I take from this video, thanks a ton
My God mate, you're an excellent teacher!!! Best explanations of tech I've heard in my life. Also your triceps are on point 🤟
Crisp and Clear. Explanation is too GOOD
🎯🎯
the way you explained concept makes micro service + service mesh easier to understand. Thank you. Keep posting such videos more.
You are a genius man, few days back i was wondering that this guy needs to create a video on service mesh , & i got the surprise.
ThanKs man, keep doing good work ✌🏼
You're my favorite technical channel by far. Thanks so much for your work
This would be a fantastic prerequisite knowledge to start design distributed system.
Thanks!
By far the best technical channel I've ever seen, really nice content! A suggestion: chaos engineering.
Beautifully explained
Awesome clarity. Honestly i got lost with the topic with other UA-cam videos
This nails exactly what it is. You rock!
Very clear and simple to understand the necessity of service mesh. Thank you so much, you save me a lot of time
You are awesome. Your content is very easy to understand and go deep to technical. Thank a lots
really nice and strait forward explanation. I love your videos
I don't know how to thank you, You helped me a lot in understanding the service mesh technology.
You are doing a great job.Please continue doing.
I would like you should bring all new things developed around kubernetes.
thank you for all the amazing lessons :)
Phenomenal channel. Love this guy so much !
What an excellent video! By far the best introduction to docker, kubernetes, and service mesh that I've ever found. You deserve 10x more subscribers.
7.5k subscribers!! Waw!! You are doing absolutely great!
Very informative service mesh video. Waiting for the future servicemesh videos too. Please include Kiali network view component in those if possible. Great job!
This is a very good intro to service meshes.
Super cool explanation, I love u DevOps Guy, many thanks!!
the traffic lane analogy for explaining the metrics of requests sent by service A and received by service B was awesome.. only that in the visual, A was receiving because traffic was incoming and B was sending cos traffic was going away :D
"If you can't explain it simply, you don't understand it well enough." -Albert Einstein,
And you Sir, You know your stuff! Love your videos, They just hit the nail on t he head.
Great content, easy to follow and digest. Thanks
awesome video thanks Marcel 👍
Thank you :) I like the way you explain in the videos
Anytime better than paid videos.. Thank you
Love your tutorials. Service Mesh - just what I was waiting for so long. Thank you!
Thank you for this amazing content.
Thanks for your great explanation!!!
beautiful video! Thanks!!!
Awesome! Really excited to learn.
amazing teacher
Finally, Thanks for this lovely content.
Thanks for sharing, also interested to see how to manage the network latency.
where did you get that Nginx ingress controller config from?
More content on this watched whole video excited to see more .
what do you bench?
Did you make it in 13:37 time deliberately?
Really interesting topic, and really good video, gz
Mate when you do port forward to playlist api to port 81 locally how does my browser understand it .. I mean you refreshed localhost in the url and it got the content.. same when you deployed db then you didn’t port fwd it but still you refreshed it and got the videos .. how this works ? Sorry if it’s a stupid question
In the first part of the video I used docker compose, no port forwarding, so all services start and the content is there, that is why you can see it all. Later in the video we deploy each service, starting with videos web, at that stage, port--forward does not show any content, we deploy the next service and piece by piece you will notice content coming through in the browser.
good job :) my Master 🙏
Just awesome! But I have one question. If you have your Kubernete cluster on DigitalOcean inside one VPC network, which means that communication between pods is already secure. So what would be the use case for service mesh with TLS connection between pods?
Thank you 💪🏽 TLS between pods means the traffic is encrypted end to end. If your network is comprised, it would be increasingly difficult to sniff packets on the network.
Many kubernetes cluster contain different Environment (prod, stage, Dev), different projects or multiple tenants, so it better to secure the communication.
It is very useful session, Maximum how many cluster can we create using Kind?
How do you maintain referential integrity between the videos and playlist databases? Can you do a video on microservice architecture and SQL databases to explain how monolithic apps can be broken into microservices when they all use the same SQL database?
Ideally in world of distributed systems, services should not leak their data model and instead provide a contract thats backward compatible. In this case, playlists-api should not know how videos are stored by the videos-api. Only way to access the data is through the videos-api. The videos-api is able to change its backing service from MySQL to Redis without impacting dependent services as the contract on videos-api (accepting an ID on a GET request) remains consistent. So the videos domain is controlled by its endpoint and no other services should be able to access its database directly. I would recommend to try avoid sharing databases between services as its an anti pattern.
12 Factor is a great read on this 12factor.net/backing-services
Microservice video series sounds like a good plan 💪🏽
Can we get a detailed video on Velero cluster backup with restic please
In Internet there are a lot of documents about velero.
Depends on your configuration /setup for concerning solution
EG medium.com/techlogs/using-velero-and-restic-to-backup-kubernetes-2f0f812da4db
Will all videos in this series be so 13:37?
amazing video!!!!!!!
i am looking to learn a service mesh what would you suggest i should learn between AWS App mesh and istio?
Personally I would start with Linkerd, then Istio, then also checkout Open Service Mesh.
Linkerd is the most beginner friendly mesh out there and you can play around with all its functionality locally using a local kind cluster. It will help you understand all the functionality of a mesh.
Istio is slightly more advanced to understand, but once you've played with Linkerd, Istio becomes a real breeze.
You don't have to go too advance with Istio, just play with the basics.
And finally, Open Service Mesh, will teach you the SMI concepts which may form the foundation of service mesh implementations on Kubernetes going forward.
Linkerd ua-cam.com/video/Hc-XFPHDDk4/v-deo.html
Istio: ua-cam.com/video/KUHzxTCe5Uc/v-deo.html
Open Service Mesh : (video on the roadmap)
@@MarcelDempers great!!!!!!!!thanks for the advice
Hi, so good. Could you please make a video on session replication between pods in kubernetes?
Thanks 💪🏽I would highly recommend not to keep sessions in processes (pods), instead move session out (to something like a database). Processes should allow for concurrency (scale out) and share nothing among them.
a great read about it here 12factor.net/processes
Thanks for your awesome videos.... Looking forward for more videos on ServiceMesh. My question is how does videos-web container integrated with videos-api & playlists-api? How does Videos-web know about Videos-api/playlist-api?
In this simple demo, videos web runs as a web app (html). It has the URL of playlist api and accesses it via GET call. Videos Api is private and Playlists API is accessing videos API using a GET call over private DNS.
This will evolve and an Ingress gateway will be introduced.
See full docs here
github.com/marcel-dempers/docker-development-youtube-series/blob/master/kubernetes/servicemesh/readme.md
Please made a video on kafka and zookeeper in k8s!
Thanks a lot for the great content man, slightly off topic but there's been some buzz in 2020 regarding Container Operating Systems (BottleRocket, FlatcarLinux, Fedora CoreOS etc..). Is this topic in your rader ?
I've heard about these, definitely going on the radar 💪🏽
I would really love to support this channel. Expect me to pay
How is this different or how does it relate to a APM product, say NewRelic?
It's very different. NewRelic integrates at code level (SDK) so it gives deep observability into method\function tracing and instrumentation. NewRelic would compare more to Prometheus + Jaeger to a degree. Service mesh gives you more network level tracing focusing on endpoints. I.E When service A calls B, B's endpoint took 5ms to respond, but it does not instrument the code of endpoint B which is what NewRelic would do if that makes sense 💪🏽
Awesomeness
Small suggestion: You should use bigger font size and lighter theme when showing the code.
Nice
Love there videos, but please make the graphics slow down, watching images bump around the screen so fast is distracting.
Best
Yeah
noice!
Great video with a lot of useful information! The animation is too dynamic and annoying though, it is difficult to read.
I feel stupid (a compliment)
Hey first to comment