{"id":42690,"date":"2016-11-30T11:40:52","date_gmt":"2016-11-30T06:10:52","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=42690"},"modified":"2016-12-05T16:05:57","modified_gmt":"2016-12-05T10:35:57","slug":"why-cios-should-adopt-containers-technology","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/why-cios-should-adopt-containers-technology\/","title":{"rendered":"Why CIOs Should Adopt Containers Technology?"},"content":{"rendered":"

Container service is not new, it was built around ten years ago in Linux environment also known as Linux container (LXC). But today, docker is most popular and has\u00a0become synonymous to containers. So before talking about some container technologies<\/a> like Docker, Kubernetes, we have to understand what container service\u00a0is, and what is the\u00a0difference between VMs and Container Technologies.<\/p>\n

\"roundup\"<\/p>\n

What is Container Technology?
\n<\/b>It is a solution to a problem to run your application\/software reliably when moving from one computing environment to another environment having the same type of kernel. This could either be from staging to the production environment or from physical machine to virtual machine in a cloud<\/a>. It wraps up\u00a0a piece of software in a complete file system that contains everything it needs to run.<\/p>\n

In container technologies, each containerized application, run on a single operating system and shares kernel with the other container, which makes containers incredibly lightweight. Shared part of the kernel are read only; every container has its own mount point for writing purpose. This means every container is isolated (Isolate process, network, and file system) from other.<\/span><\/p>\n

Difference Between Containers and VMs.
\n<\/b>A container is not VM, it\u2019s just a process which has its own namespaces. VMs run entire operating system whereas each container runs a single process.<\/p>\n

\"VM-Diagram\"<\/span><\/p>\n

In a larger infrastructure, running VMs means probably running many duplicate instances having the same type of OS which may cause overhead to your host machine. As containers are lightweight compared to VMs, we can run around 10 to 11 times as many containers as VMs on the same hardware.<\/span><\/p>\n\n\n\n\n\n\n\n\n\n\n
Description<\/b><\/td>\nContainer Services<\/b><\/td>\nVM<\/b><\/td>\n<\/tr>\n
Isolation<\/span><\/td>\nProcess Level<\/span><\/td>\nComplete<\/span><\/td>\n<\/tr>\n
OS<\/span><\/td>\nLinux<\/span><\/td>\nLinux, Windows, <\/span><\/td>\n<\/tr>\n
Start Time<\/span><\/td>\nSeconds<\/span><\/td>\nMinutes<\/span><\/td>\n<\/tr>\n
Building Image Time<\/span><\/td>\nShort (minutes)<\/span><\/td>\nLong (10+ minutes)<\/span><\/td>\n<\/tr>\n
Hosted Number<\/span><\/td>\nOn 1 machine you can run 15 containers<\/span><\/td>\nOn 1 machine you can run few VM\u2019s (2-3)<\/span><\/td>\n<\/tr>\n
Deployment Tools<\/span><\/td>\nKubernetes, Docker Swarm, Mesos<\/span><\/td>\n<\/td>\n<\/tr>\n
Size<\/span><\/td>\n100Mb +<\/span><\/td>\n1 Gb +<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Benefits of containerization<\/strong><\/p>\n