One of the best breakdowns of VM vs Container I have seen on YT. Thank you! As I always say if you can't break it down to a 5 year old then you don't know it well enough :)
My goodness, why are you the first person to concisely describe the difference between VMs and containers? Of all the lectures, conferences, and tutorials I've seen, I either get a complete deep dive of how containers came to be, or I get "it's basically magic but it does cool stuff".
Maybe because it is the terminology from the network's perspectives, to provide, and it is not both a technical terminology, nor the legal definition of the structure, OR the technical concept, which can indeed be patented you know ? THAT is the problem which we are dealing with today. 1) Laymen terms to describe something. 2) Technical vendor's term, and that they licensed and patented this. 3) Academic research and published terminologies... and peer accepted, and reviewed. (This is the ONLY term that anybody can use in an open source concept. Only public, in terms of its citizens within that country, mind. And no other countries can use it. Unless they have trade deals or treaties etc.)
The comparison of containers and VM is brilliantly understood. Very clear information, in particular how they can work together as well. Awesome. Thank you!
Are the three apps that were (in the VM case) running on 3 different O/S's now required to all be ported to one OS or does the container runtime provide that abstraction so each app can continue to assume its talking to Windows/BSD/Linux?
You typically run a full OS on your host, e.g. Ubuntu and a lightweight Linux distro inside each container, e.g. Alpine. Would you call Alpine a Guest OS in that case or what's the right terminology?
the image contains all the code and libraries necessary to run your application. A container depends on the image to create the run-time environment for that application.
@@devcentral : I realised that this was made in 2018... and my working life's experiences had been splitting inbetween that singular stack (3-tier architecture), to this kind of multiple stack (aka "distributed computing").... form. I just wanted to state that... when his point about dropping the entire 3-tier stack into one of the slots, as a virtual machine, and still make it work. This is not entirely true. There has to be adaptation, and further configuration in order for such machines to work effectively. This is well known. Because the way that the codes work, had always been to work in a specific and explicit way. There still has to be further reconfiguration of existing codes, or entire rewrite of various codes. So this is not entirely true. - I know, cos I used to deal with such fallouts, and the Network guy always said "it should work" !... And in truth, the recommended specification of those apps, are often based on a 3-tier architecture to run to begin with. And there hasn't been white papers that was published by the vendors to support split architectures and virtualise this. Often, exceptions and separate API has to be written to make it work... Which itself makes it cumbersome to maintain. This is the reality really. The virtualised distributed stack is now the "cloud" isn't it ? Becoming much larger in size...
@@MeiinUK I don't see it as much of an industry standard truth as a technically possible truth. Personal labs are quite often built on consolidated stacks. In fact, I have an entire F5 distributed cloud edge computing environment running in a KVM virtual machine on my Intel NUC in my office. For production deployments, whether the focus is performance, scale, services, security, etc, there will always be architectural advantages to segmenting, whether it's completely contained within a multi-node cluster, or a multi-node cluster with ingress and egress services, or multi-cloud, or multi-cloud with on-prem, or... Business requirements, security policy, cost, and architecture teams will drive that conversation and need ultimately.
@@JasonRahm : You have to remember that we live in an un-precedented times. Whereby, logical and digital text..(never mind audio, and digital video)... just digital text itself, was indeed based on certain architectures... and now, with the combination of both texts, audio, and video, all combined into a single thing... on top of the fact that, we have basically ruined "life" as we know it ? When advertising tech, combines and overwrite that of medical tech... or over write political tech (voting systems, and the news)..... And everything now becomes a "retail tech"... Where do you draw this line? I still remember when a "phone" IS a phone, a "TV" IS a TV.... And now... ruined. With these so called "compounded architecture, to have the TV channel on the same cloud base or the same machine as the voting system". This has TO stop. Do you realise this ? The word, "container" I have not heard of , in my uni days.. nor amongst my peers. So it must've been coming from the network side. When applications and OS level people, come together with those of the network side.. I mean.... He means the implied "3 tier architecture"... when he said that entire contained "stack". I do not know what is "edge computing", or what is classified as such, in the context of the architecture itself. And even then... some people do not call the OS, combined with the hardware, to be classified as "architecture"... I noticed that he classified the bottom tier as "infrastructures" and not the "hardware tier".... You need to implicitly understand something, many of the laws in different countries, are explicit, based on the definition of such items... and its surrounding laws. I don't even understand what you mean when you say "personal lab".... In the UK, it is very simple. I, the "citizen" is not the "sole trading company", and is not the "limited company" that I may work in. "I", the citizen, is not the employee, and is not the sole trading company, and is not the limited company. Because for you to say that "I" the citizen.. is now not the citizen, but it is now the sole trading company, when I have not registered as such.. and is not running a company... is a bit of a misnomer.
@@JasonRahm : To be honest, I did not expect F5 to be broadcasting this kind of commercial info, to the "public" realm.. It is normally, and often, locked inside a company, or locked inside the access for their customer's employees to learn... and not this global way.. (which UA-cam/Google has a reach of)..... This is crazy.
linux containers on windows works because there is linux support with add-ins, but the other way around is not possible last I researched. You can use tools like wineHQ to run windows apps on linux though.
Why did you use 'type 2 hypervisor' in your presentation? This type is not commonly used in a real production environment. 'Type 1 hypervisor' is installed directly on the physical hardware of the host server, just like the operating system. So, in this case, you do not need an additional host OS - this is one of the biggest advantages of virtualization
Hi Anton, thanks for the feedback! I used both as a means of clarification of the different abstraction techniques employed, whether for test or production. You are certainly correct that for virtualization in a production environment that bare metal is best.
Containers are just a deployment strategy for an application, the application itself is the service deployed IN the container that a client interacts with.
Thank you for creating this simple and yet precise explanation. Drives home the point succinctly.
One of the best breakdowns of VM vs Container I have seen on YT. Thank you! As I always say if you can't break it down to a 5 year old then you don't know it well enough :)
Glad you liked it and we appreciate the comment!!
Definitely the most understanding video about container! Thanks.
My goodness, why are you the first person to concisely describe the difference between VMs and containers?
Of all the lectures, conferences, and tutorials I've seen, I either get a complete deep dive of how containers came to be, or I get "it's basically magic but it does cool stuff".
Thanks for the encouragement!
Maybe because it is the terminology from the network's perspectives, to provide, and it is not both a technical terminology, nor the legal definition of the structure, OR the technical concept, which can indeed be patented you know ? THAT is the problem which we are dealing with today.
1) Laymen terms to describe something.
2) Technical vendor's term, and that they licensed and patented this.
3) Academic research and published terminologies... and peer accepted, and reviewed. (This is the ONLY term that anybody can use in an open source concept. Only public, in terms of its citizens within that country, mind. And no other countries can use it. Unless they have trade deals or treaties etc.)
The comparison of containers and VM is brilliantly understood. Very clear information, in particular how they can work together as well. Awesome. Thank you!
glad you enjoyed it!
Thanks! The best explanation I've seen so far
Definitely subscribing!!! Thank you. You're good at explaining.
Excellent!!! Very well explained; in fact the best so far amongst all the other videos explaining containers.
This is awesome, think I'm finally grasping this stuff, thanks!
Great Video!! Very easy explanation with the foundational concepts.
You are really the best!!!
The explanations from you is better that from Microsoft :(
We appreciate the comment!
Simple explanation to a complex topic!
EXCELLENT job! You just taught me what containers are :)
You are absolutely the best . You explained it so well !
Best so far
very simple and sweet explanation, great work.
Great , Stunning
thanks for the note!
Excellent video, excellent content. Well done.
Are the three apps that were (in the VM case) running on 3 different O/S's now required to all be ported to one OS or does the container runtime provide that abstraction so each app can continue to assume its talking to Windows/BSD/Linux?
Really simple explanation .
Great video. Very useful and easy to understand. Gracias!
Great Explanation! Thank you
You typically run a full OS on your host, e.g. Ubuntu and a lightweight Linux distro inside each container, e.g. Alpine. Would you call Alpine a Guest OS in that case or what's the right terminology?
I would say your base image contains a a lightweight Linux that utilise the Undelaying OS system.
Great video congratulations 👏👏👏
That was a great video, thank you!
Fabulous! Keep going guys!
Could you brief about the details on what is a Container Image, curious to understand..
the image contains all the code and libraries necessary to run your application. A container depends on the image to create the run-time environment for that application.
How is he writing all this? is it done in post or is it some sort of sensor?
thanks for the comment! you can see how we do it here: ua-cam.com/video/U7E_L4wCPTc/v-deo.html
do all the bin/lib(s) use the same operating system? If we wanted to run a lib/bin on BSD and Linux, would we have to have 2 different containers?
if theres already host os, do we get to decide type1 or type2 hypervisor??...bcoz type 1 is bare metal right!!?
no hypervisor at all with containers, just *jailed* processes necessary to run the application of record.
Nicely explained. Thankyou...
simple n informative ! :)
Never knew that was what containers are. Interesting.
Glad you liked it and thanks for the comment!
@@devcentral : I realised that this was made in 2018... and my working life's experiences had been splitting inbetween that singular stack (3-tier architecture), to this kind of multiple stack (aka "distributed computing").... form. I just wanted to state that... when his point about dropping the entire 3-tier stack into one of the slots, as a virtual machine, and still make it work. This is not entirely true. There has to be adaptation, and further configuration in order for such machines to work effectively. This is well known. Because the way that the codes work, had always been to work in a specific and explicit way. There still has to be further reconfiguration of existing codes, or entire rewrite of various codes. So this is not entirely true. - I know, cos I used to deal with such fallouts, and the Network guy always said "it should work" !... And in truth, the recommended specification of those apps, are often based on a 3-tier architecture to run to begin with. And there hasn't been white papers that was published by the vendors to support split architectures and virtualise this. Often, exceptions and separate API has to be written to make it work... Which itself makes it cumbersome to maintain. This is the reality really.
The virtualised distributed stack is now the "cloud" isn't it ? Becoming much larger in size...
@@MeiinUK I don't see it as much of an industry standard truth as a technically possible truth. Personal labs are quite often built on consolidated stacks. In fact, I have an entire F5 distributed cloud edge computing environment running in a KVM virtual machine on my Intel NUC in my office. For production deployments, whether the focus is performance, scale, services, security, etc, there will always be architectural advantages to segmenting, whether it's completely contained within a multi-node cluster, or a multi-node cluster with ingress and egress services, or multi-cloud, or multi-cloud with on-prem, or... Business requirements, security policy, cost, and architecture teams will drive that conversation and need ultimately.
@@JasonRahm : You have to remember that we live in an un-precedented times. Whereby, logical and digital text..(never mind audio, and digital video)... just digital text itself, was indeed based on certain architectures... and now, with the combination of both texts, audio, and video, all combined into a single thing... on top of the fact that, we have basically ruined "life" as we know it ? When advertising tech, combines and overwrite that of medical tech... or over write political tech (voting systems, and the news)..... And everything now becomes a "retail tech"... Where do you draw this line? I still remember when a "phone" IS a phone, a "TV" IS a TV.... And now... ruined. With these so called "compounded architecture, to have the TV channel on the same cloud base or the same machine as the voting system". This has TO stop. Do you realise this ?
The word, "container" I have not heard of , in my uni days.. nor amongst my peers. So it must've been coming from the network side. When applications and OS level people, come together with those of the network side.. I mean.... He means the implied "3 tier architecture"... when he said that entire contained "stack".
I do not know what is "edge computing", or what is classified as such, in the context of the architecture itself. And even then... some people do not call the OS, combined with the hardware, to be classified as "architecture"... I noticed that he classified the bottom tier as "infrastructures" and not the "hardware tier"....
You need to implicitly understand something, many of the laws in different countries, are explicit, based on the definition of such items... and its surrounding laws.
I don't even understand what you mean when you say "personal lab"....
In the UK, it is very simple. I, the "citizen" is not the "sole trading company", and is not the "limited company" that I may work in. "I", the citizen, is not the employee, and is not the sole trading company, and is not the limited company. Because for you to say that "I" the citizen.. is now not the citizen, but it is now the sole trading company, when I have not registered as such.. and is not running a company... is a bit of a misnomer.
@@JasonRahm : To be honest, I did not expect F5 to be broadcasting this kind of commercial info, to the "public" realm.. It is normally, and often, locked inside a company, or locked inside the access for their customer's employees to learn... and not this global way.. (which UA-cam/Google has a reach of)..... This is crazy.
Nice explanation !
What is the average lifespan of container?
So containers are EXE file in this case ?
very nice explanation
So when can we use containers to run Windows programs in Linux???
linux containers on windows works because there is linux support with add-ins, but the other way around is not possible last I researched. You can use tools like wineHQ to run windows apps on linux though.
Why did you use 'type 2 hypervisor' in your presentation? This type is not commonly used in a real production environment.
'Type 1 hypervisor' is installed directly on the physical hardware of the host server, just like the operating system. So, in this case, you do not need an additional host OS - this is one of the biggest advantages of virtualization
Hi Anton, thanks for the feedback! I used both as a means of clarification of the different abstraction techniques employed, whether for test or production. You are certainly correct that for virtualization in a production environment that bare metal is best.
Thanks, how can i a video like this pleas?
Are you asking how you can shoot a video like this? See here for details: devcentral.f5.com/s/articles/lightboard-lessons-behind-the-scenes
What's an application in this context
Containers are just a deployment strategy for an application, the application itself is the service deployed IN the container that a client interacts with.
I have to ask, are you writing backwards or is this some technology that a mere peasant such as myself doesn't know of yet?
Details on our build: devcentral.f5.com/s/articles/lightboard-lessons-behind-the-scenes
Thanks!
Nice explanation
You sir, yes you! You RoCk!
Super
i dont get it
Aren't you the guy from the movie She's out of my league?????
don't have that skill set but if you track him down, I'll be happy to share his royalty checks!
what a waste fo time!