He's writing on a panel of glass that has been placed between the camera and the presenter. And then, in post-production, the video is flipped horizontally. (Notice that his shirt pocket is on the wrong side!)
This guy's really deserves respect. In the year when we were not knowing about digital board this guy just made video on light board . Respect gained sir 👏👏👏
I am working 12+ hours a day right now trying to learn as much as I can about web dev, so I'm currently ingesting a lot of tutorial content. With that in mind I can say that you are by FAR the best orator/tutor I've come across in a long time! Max respect :)
I'm really impressed with the explanation as well as the lightboard which has been used. Most tutors use traditional whiteboards or PowerPoint presentations. Technically and content wise this lecture is a class above.
IBM ...please find a way to clone this guy. The world needs more excellent instructors like him. Excellent presentation and gives a clear understanding of the material .
A great overview. Seen multiple resources on containerization. Since I don't need to understand it in-depth, this has really helped me and I have to say I really get what it's all about for the first time. Thank you!
Excellent job! This succeeded in explaining containers to me where all else failed. Thank you very much for your time and research into making this digestible.
This is helpful. So in essence, containers and VMs are similar in that they're both ways to scale computing resources. Containers are more scalable than VMs because they don't need to virtualize the OS every time.
I have not seen any business package/host application in VMs as their deployment solutions. Virtualization use case is more of abstracting hardware (bare metal hypervisor). I think the whole idea of Containerization is built around the benefits that you have explained.
Man, you're great! keep it up! I was really suffering with the many useless resources about the same exact thing! but you just did it right! realllllllly thanks!
Thank you for this video. One question - images are often build upon an OS-base such as "FROM ubuntu:22.04" etc. Even though they are more ligthweight, they are still OSes. In your schema, wouldn't it be more accurate to keep the OS layer for containers too? The difference between VMs and conts. could be then attributed to the kernel. (VM its own drivers etc?)
2:56 Are all incompatibility problems resolved when dev/customer apps/libs are the same? Or some issues get squashed by making dev/customer's guest OS be the same as well?
It's true that if you run docker containers on windows or macos it still has to run in some kind of linux virtualization though, right? I think the virtualization would still be shared between the containers at least though, instead having to be recreated for each unit.
You mentioned applications might work on your local machine during development but break when pushing to your VM, which screws up CI/CD, however I missed why containers fix this. Why is that?
Because of its portability, your application is running in a container, which is an isolated environment which provides everything you need for running an application, so you just need to build an image for your application once, and run it everywhere, whatever it is in physical server, virtual server or cloud environment. And it also standardize the process of deployment, you just need to run a command docker build/run to deploy.
A few reasons to use containers rather than VMs: 1. Lighter weight: no need to run an OS in a container comparing to a VM 2. More resource efficient: 1. no extra OS needed to be run in containers; 2. resources in the hosted node can be shared dynamically
Question: I can understand where there is no hypervisor when running the containers, can you tell us why no OS is needed or is there a base OS already on each of the containers?
Thanks for the video. I'm new to software and i have a #question on duplication of OS in containerzation. Lets say we have an java application and trying to create an container of the java application(assuming each container will have its own run time environment).Once the java application container is created, jvm in the container has to co-ordinates with "OS". In this case jvm will co-ordinate with which "OS". If jvm co-ordinates with "HOSt OS", In that case if we have an another application where its runtime evironment that doesnt support the "Host OS". what are our options? If jvm co-ordinates with "OS in the container",that means the container will have its own "OS" apart from the "host os". In this case if we scale the application, container duplicates the "OS" right ? Please correct me if my understanding is wrong ?
To start off, great video I did have a couple questions. So these examples are based on Type 2 Hypervisors That would not be like that in production, was there a reason for that choice? Or are you referring to a diff Host OS than that? 2nd which is why I was orginally watching 😊 What would be the production scenario for containers, Type 1 hyper with a linux vm server with runtime and spin the containers from there? Ty!
What a great presentation! Very engaging and doesn't require amazing feats of concentration to learn the information from you! :-) Good work presenter.
Thanks great presentation. Can you share what presentation tools you used on this video? It's cool to see a transparent board with you in the background.
In the VM scenario, why do you have to spin up multiple Linux OSes to run multiple copies of your app? is it not possible to run multiple copies on the same OS?
2:58 When it doesn't work after deployment in prod, isn't it a networking issue? Issues and incompatibilities between coding on a mac book and deploying it in a hyper-visor environment seems a little bit like a stretch. At least in my experience, it seems like the network guy messed with some firewall somewhere and is messing up the code.
Hi Greg: Apps breaking when deploying in another environment can result from a number of issues - for example, file system calls which are OS-specific. Having a consistent environment via containerization helps limit those issues. Thanks for watching, Sai
LOL In 17 yrs I have had developers blame the network thousands of times. It has actually been the network perhaps half a dozen times. It is a network issue is the laziest form of troubleshooting and hand washing technique known to IT. Stop.
I missed the WHY we don't need the "guest OS" in containers. I see you said its better coz it would be light weight without the OS but what compensates for the OS
There's an INCORRECT assumption being made in the accounting for resource consumption at @1:45: The presenter is assuming that VM's are hosted on a Type II hypervisor (i.e., A hosted hypervisor). Production workloads are run on Type I hypervisors that don't have an underlying O/S . (e.g., Bare metal hypervisors like Xen, VMware ESX, etc). Therefore Type I hypervisors consume fewer host resources and don't incur the performance penalty of Type II hypervisors.
2:54 Agile DevOps
3:25 3 steps to create Container:
1.manifest: Docker file or YAML(Cloud Foundry);
2. image:Docker image or ACI "Application Container Image"(Rocket);
3.container itself:
4:16 Docker Engine
5:45 example: cognitive API + Python application + .js application
For a moment, I was super impressed that he could write backwards!
smart board technology
me too
He's writing on a panel of glass that has been placed between the camera and the presenter. And then, in post-production, the video is flipped horizontally. (Notice that his shirt pocket is on the wrong side!)
@@epretorious Thanks, I was having a tough time visualizing what was happening here.
notice they all left-handed
What a clear and crisp presentation Sai. The way IBM is advocating for Cloud is totally appreciable. count me in...soon.
This video 'Contains' almost everything that will help to get a good overview of Containerization. Great Work!
This guy's really deserves respect. In the year when we were not knowing about digital board this guy just made video on light board . Respect gained sir 👏👏👏
Wow one of the more amazing tech presenters out there!
Absolutely, one of the best explainers I've seen so far. His handwriting is gorgeous as well.
nice to read from you
I am working 12+ hours a day right now trying to learn as much as I can about web dev, so I'm currently ingesting a lot of tutorial content. With that in mind I can say that you are by FAR the best orator/tutor I've come across in a long time! Max respect :)
Hi Adam! Honored to be able to help with your educational journey. Best of luck to you in your future endeavors! -Sai
how did it go working those hours - where are you now compared to where you were 3 years ago? 🙂
@@IBMTechnology how can i sign up to have classes with you ?
@@IBMTechnology how can I register for a class with you guys and get the certification.
@@clarkflavorprobably died
Great high-level overview of containers vs VMs.
I'm really impressed with the explanation as well as the lightboard which has been used. Most tutors use traditional whiteboards or PowerPoint presentations. Technically and content wise this lecture is a class above.
I think they flipped the video.
My man is killing it. I'm gonna watch the entire playlist. Thank you in advance!
One of the ONE trainers, Sai Vennam. Thank you! Great content in all of your videos.
IBM ...please find a way to clone this guy. The world needs more excellent instructors like him. Excellent presentation and gives a clear understanding of the material .
I really love these videos; great information presented cleanly and concisely.
I liked the way you compare VMs with Containers. It made it very easy to understand the fundamentals with details. Thanks!!
A great overview. Seen multiple resources on containerization. Since I don't need to understand it in-depth, this has really helped me and I have to say I really get what it's all about for the first time. Thank you!
We're so glad to hear this! And thank you for the appreciation! 👍
Excellent job! This succeeded in explaining containers to me where all else failed. Thank you very much for your time and research into making this digestible.
Wow this dude is great I need him for my exams
Explained the concept in Simple and Crisp way.... Amazing work Sir......
One of the best explanation of why containerization is important
before watching this, didn't have any idea about containers. Now its all clear. thanks.
Finally... a clear run-through of containers. good lad
The comparative example made it much easier to understand the concept of containerization.
This is helpful. So in essence, containers and VMs are similar in that they're both ways to scale computing resources.
Containers are more scalable than VMs because they don't need to virtualize the OS every time.
I have not seen any business package/host application in VMs as their deployment solutions. Virtualization use case is more of abstracting hardware (bare metal hypervisor). I think the whole idea of Containerization is built around the benefits that you have explained.
Really good stuff! Perfect for when you'd like to get a basic understanding of the technology and the differences between them!
Man, you're great! keep it up!
I was really suffering with the many useless resources about the same exact thing! but you just did it right! realllllllly thanks!
very eloquently explained Sai...Great job. Love your explanation and presentation skills
This is the best explanation I have ever heard. Great job!!!
Thanks.
You explained such way that I could capture it easily.
Simply straightforward.
Liked the simple way of explaining the concept and impressed by the graphics!
Glad to hear that! Thank you!
Hi Sai! Greetings from Argentina! I want to thank you for your video! And I want you to know that they are helping us very much with our learnings!
Stefania we are really happy this was so helpful to you! Thank you for watching.-Sai
I comment really rarely - this is the best out there.
Best explanation of VMs vs containers to date... thanks!!!
I'm most impressed by the flawless backwards writing
so after months of research, i now understand the docker / K8 architecture. It was a damn long process but this video helped put as well
That is one of the best explanations I've ever seen! Amazing job, Sai. Congratulations!
Brilliant comparison and conceptualisation. Keep posting more videos guys. Thanks Sai!!
Absolute clear and crisp articulation
Thank you! 😃
this is best expleination i found on youtube...
Thank you for this video.
One question - images are often build upon an OS-base such as "FROM ubuntu:22.04" etc. Even though they are more ligthweight, they are still OSes. In your schema, wouldn't it be more accurate to keep the OS layer for containers too? The difference between VMs and conts. could be then attributed to the kernel. (VM its own drivers etc?)
Very Well Explained. I am sure I am not going to forget this "vision" about containers. Keep up the good work.
He made containers so amazingly simple.
Thanks a lot. Enjoyed and Understood. It was nice that you explained it with example.
You're welcome!
This video really helped me understand containers....thanks Sai Vennam!
2:56 Are all incompatibility problems resolved when dev/customer apps/libs are the same? Or some issues get squashed by making dev/customer's guest OS be the same as well?
Totally to the point! Glad I viewed this video.
Amazing explanantion of what containers are and how they are used. Thank you!
Thanks for explaining the containers in a very simple way
When we talk about "the shared pool of resources", does it refer to the RAM and CPU?
Excellent explanation of the benefits of containers. Great overview!
finally clean explanation on containerization, thank you
You're welcome, Fateh. Be sure to check out our channel for more videos on containerization. 👍
What are pros and cons of using just the containers on top of Host OS vs running containers on top of VMs (and VMs on hypervisor) ?
Sai you are a wizard at explaining some of these concepts. Keep it up!
It's true that if you run docker containers on windows or macos it still has to run in some kind of linux virtualization though, right?
I think the virtualization would still be shared between the containers at least though, instead having to be recreated for each unit.
bro I have been looking for you. Million Thanks
You mentioned applications might work on your local machine during development but break when pushing to your VM, which screws up CI/CD, however I missed why containers fix this. Why is that?
Because of its portability, your application is running in a container, which is an isolated environment which provides everything you need for running an application, so you just need to build an image for your application once, and run it everywhere, whatever it is in physical server, virtual server or cloud environment. And it also standardize the process of deployment, you just need to run a command docker build/run to deploy.
Great explanation ! ! but, Where are the manifest, image, and the container located? and what resources are they drawing from?
A few reasons to use containers rather than VMs:
1. Lighter weight: no need to run an OS in a container comparing to a VM
2. More resource efficient: 1. no extra OS needed to be run in containers; 2. resources in the hosted node can be shared dynamically
Something I don't get is - if we want to just run applications and choose vm, why do we need multiple virtual machines for each app?
Hey Sai, excellent illustration on containerization. appreciate your time for sharing your knowledge. Thanks !!. Mat.
This might be a dumb question , but isn’t hypervisor doing the virtualization on the hardware and not the host OS?
I just realized that you had to write backwards for this. Awesome.
They filp the video. He is right handed
Question: I can understand where there is no hypervisor when running the containers, can you tell us why no OS is needed or is there a base OS already on each of the containers?
Containers use host computer OS. Thats the whole point of having containers. Containers don't have overhead of keeping or running OS.
lucid explanation, thanks! Keep posting more.
This helped me out a LOT as an IT recruiter. Thanks!
I have no idea why the other UA-camr's forgot to mention the Guest (Host OS) which is everything for this concept, you're Amazing
what resources do you refer too when you say after production it consumes resources?? Can you please specify?
what about VM with Type 1 hypervisor along with the containers ? wouldn't be a good approach ?
In the first case, Could we don't use VM and just deploy applications on host OS? We don't need to install Linux VM, just use Linux Server.
Good explanation for each term. Easy to understand.
Thanks for helping me with learing about Containers
Outsanding skills. You are one in a million!
Thank you, RJ!
Thanks for the video. I'm new to software and i have a #question on duplication of OS in containerzation.
Lets say we have an java application and trying to create an container of the java application(assuming each container will have its own run time environment).Once the java application container is created, jvm in the container has to co-ordinates with "OS". In this case jvm will co-ordinate with which "OS".
If jvm co-ordinates with "HOSt OS", In that case if we have an another application where its runtime evironment that doesnt support the "Host OS". what are our options?
If jvm co-ordinates with "OS in the container",that means the container will have its own "OS" apart from the "host os". In this case if we scale the application, container duplicates the "OS" right ?
Please correct me if my understanding is wrong ?
Is it me or is anyone else noticing how good his backwards writing is?
Can you have more than one app deployed on the same guest OS? (In the case of non-containerized solution).
To start off, great video
I did have a couple questions.
So these examples are based on Type 2 Hypervisors
That would not be like that in production, was there a reason for that choice?
Or are you referring to a diff Host OS than that?
2nd which is why I was orginally watching 😊
What would be the production scenario for containers, Type 1 hyper with a linux vm server with runtime and spin the containers from there? Ty!
What a great presentation! Very engaging and doesn't require amazing feats of concentration to learn the information from you! :-) Good work presenter.
Thanks for watching, Chris! Appreciate your feedback.
Love the series
Thanks great presentation. Can you share what presentation tools you used on this video? It's cool to see a transparent board with you in the background.
great video!! do "What is Cloud Native?" next!
Another great presentation from Sai, really easy to follow and very personable. Well done!
Great video. Super useful
This guy is really good sharing his knowledge. Thanks!!!
In the VM scenario, why do you have to spin up multiple Linux OSes to run multiple copies of your app? is it not possible to run multiple copies on the same OS?
Very well explained containerisation concepts.
Great presentation which clearly demonstrates many of the benefits of lightweight containers v heavyweight virtual images
2:58 When it doesn't work after deployment in prod, isn't it a networking issue? Issues and incompatibilities between coding on a mac book and deploying it in a hyper-visor environment seems a little bit like a stretch. At least in my experience, it seems like the network guy messed with some firewall somewhere and is messing up the code.
Hi Greg: Apps breaking when deploying in another environment can result from a number of issues - for example, file system calls which are OS-specific. Having a consistent environment via containerization helps limit those issues. Thanks for watching, Sai
LOL In 17 yrs I have had developers blame the network thousands of times. It has actually been the network perhaps half a dozen times. It is a network issue is the laziest form of troubleshooting and hand washing technique known to IT. Stop.
I missed the WHY we don't need the "guest OS" in containers. I see you said its better coz it would be light weight without the OS but what compensates for the OS
There's an INCORRECT assumption being made in the accounting for resource consumption at @1:45: The presenter is assuming that VM's are hosted on a Type II hypervisor (i.e., A hosted hypervisor).
Production workloads are run on Type I hypervisors that don't have an underlying O/S . (e.g., Bare metal hypervisors like Xen, VMware ESX, etc).
Therefore Type I hypervisors consume fewer host resources and don't incur the performance penalty of Type II hypervisors.
This explanation helped me a lot.
Thanks, very simple and straight to the point!
Thank you, Javier!
just starting to learn--very helpful as an overall explanation!
Superbly explained
Perfect, simple and straightforward
Glad it was helpful Carolyn. Appreciate you watching!
He's really good at writing backwards
Nicely presented and explained. Thanks!
I'm just curious how do you write in reverse way but still fast? :)
Wishing you smiles through it all.
Wow, great explanation!
Yes, Indeed!
Men I thought IBM had such really nice content