VMs vs. Containers: When to Use Each

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

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

50% 1

Containers won’t replace VMs: searchservervirtualization.te...
Virtual machines and containers are two approaches that loosen the traditional dependence computer applications have on servers and operating systems. Choosing between VMs or containers is an application-dependent decision; Virtual machines are generally deployed when users need different operating systems and processing power for different applications running simultaneously, while containers are often used when multiple applications using the same OS are needed.
What approach or combination of approaches does your organization use, and why? Share your thoughts in the comments, and be sure to hit that like button, too.
Stay up to date on the latest server virtualization software news: searchservervirtualization.te...
Follow us on Twitter: / @tt_infra
Like us on Facebook: / techtargetinfrastructure
#VMvsContainer #ContainervsVM #ServerVirtualization

Наука

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

28 мар 2021

Ссылка:

Скачать:

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

Добавить в:

Мой плейлист

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

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

@cadeeb 9 месяцев назад

Very nicely presented the difference between Containers and VMs with Pros, Cons and usage. I got few questions, it would be nice if you can provide some lights on it. 1) Why it is difficult to manage Admin and Security for Containers? 2) Which approach is better for migration of applications from on-prem to cloud? 3) Which approach is better for implementing micro-services? 4) Which approach is better for integration of applications (Internal within same domain and external apps)? Thansk

@nochkin 4 месяца назад

1) It's the same as with VMs. You need to find the right tools and it becomes easy 2) Containers 3) Containers 4) Depends, but most likely it's containers too

@pedrobarrosmarzano6675 3 года назад

Cool explanation. Thanks

@EyeonTech 3 года назад

You're welcome!

@theonlyxem Год назад

Can you run containers on top of VM rather than physical servers like what u stated?

@CloudGrazingZebra 9 месяцев назад

Yes, this is a common approach. A hypervisor can be created on the physical server which can be used to create multiple virtual machines. You can create virtual machines potentially using ISO images with your chosen OS to act as independent systems. In Kubernetes, these can be thought of as “nodes”. Lastly, these nodes are set up and connected to the cluster. Containers from a registry are deployed on the nodes as units called “pods”. These pods can run the code you wrote. There’s a number of different ways to go about using VMs and Containers. Hopefully this provides some more clarity.