Containers in the cloud enhance portability making it more comfortable, or so they would like you to think. There is another side to this story. It takes some specific knowledge of the processes and the underlying technology that makes cloud-to-cloud migration using containers a lower-effort and lower-risk endeavor. Because the required skills and best practices aren’t as available as they should be, organizations have struggled to catch up.

What Is a Container and How do They Work

Containers break up applications into smaller packages of code. Each is bundled with all the necessary system software that apps need to operate independently of whichever server is playing the host’s role. The portability of moving code and applications independently is the big selling point of containers. Containers eliminate the need for programmers to rewrite the code for each new operating system and cloud platform. Containers allow those applications to scale, as well as an asset.

Sounds great, right? Absolutely, but even with all the upsides, there are a few downsides you need to consider. There are some limitations and impediments to using containers in public and private clouds.

Container Security Boundaries and RisksContainers inherently come with security limitations. Many security admins inside an enterprise don’t understand all the details and risks of containers, so it is essential to ensure that your IT personnel work with containers to understand them thoroughly before implementing this technology. Although there have not been any significant container security breaches, hackers are becoming smarter and more knowledgeable about using containers, and these sorts of attacks will increase. With increased desire and the need for easier portability using containers, we could also be making our containerized applications more vulnerable.

Containers or VMs?

When thinking of portability, you should consider containers and think about the differences between using containers or using VMs. Virtual Machines are self-contained. Each VM has a unique operating system (OS), drivers, and application components. You can migrate VMs to any other method, as long as there is a compatible hypervisor available. Unlike Vms, containers are very different. They run on top of the physical OS, and they share much of the underlying OS kernel, along with many libraries and binaries. This means they are more tightly

Containers Can Be Messy

Moving containers to the cloud can create a mess. Because containers can be launched very quickly, they can consume more cloud resources than necessary without your IT personnel understanding why that is happening. One thing you can do to avoid creating this problem is to have an orderly shutdown of containers you are no longer using. Often, developers launch container-based applications, and then forget to go back later to scale the number of containers, locking the resources until they do.

Paving The Way 

Containers will pave the path to cloud portability. Even so, one must remember that containers are no panacea for cloud portability. There are limitations when it comes to security, application types, and deployment. Most public and private cloud providers are container friendly. With each cloud service release, cloud developers have more reasons to leverage containers for mobile application development in the cloud.

The question for containers is not whether or not to utilize them but rather how to best use the technology. Many use containers for portability and to protect themselves against cloud computing vendor lock-in. The critical thing to understand is that learning how to use containers most effectively takes time and effort. Still, as long as you commit to providing that education, you will be successful with this technology.

Dec 9 20
Christina Zumwalt
%d bloggers like this: