Key Takeaways from ContainerCon
There are many drivers behind peoples’ excitement around Linux Containers – but here are the main reasons.
Join the DZone community and get the full member experience.Join For Free
This is an overdue blog around the key takeaways from ContainerCon. We had the privilege of being a silver sponsor of this event. While we were mostly at our booth talking to conference participants, we managed to attend a couple of keynote sessions as well.
Here are the key takeaways:
There are many drivers behind peoples’ excitement around Linux Containers – but the main ones that stood out for us were:
- Application portability – being able to run the same app on any Linux host running on any cloud is like a dream come true for many sys admins and developers. Administrators are relieved that they no longer have to maintain different configuration scripts for different cloud environments and are excited about not being locked down to specific cloud provider or virtualization technology as a result.
- Quickly evolving ecosystem– Linux admins and devlopers are excited to see how quickly this ecosystem is evolving to address the various gaps in the container technology
Containers do not have to replace existing virtualization technologies – they’re absolutely complementary. Many enterprises have made significant investments in on-premise virtualization platforms like vSphere, OpenStack and CloudStack, or in public cloud infrastructure services like Amazon Web Services, Rackspace, Microsoft Azure, DigitalOcean, Google Compute Engine, etc. They, of course, would like to run containers on their virtualized infrastructure of choice – but are mainly interested in addressing the end-to-end automation workflows while applying existing access controls & policies.
Ensuring high availability by distributing containers across multiple hosts or regions is an absolute must if this technology is to be used in production.
Containerizing enterprise IT applications is still a challenge because:
- It typically involves a significant learning curve in learning yet a new syntax in Dockerfiles
- Existing application composition frameworks do not address complex dependencies or auto-scaling workflows post-provision
- Integrations with existing load balancing or database services are difficult to manage today (especially after the application has been provisioned)
We were thrilled to hear this feedback as we have addressed most of these challenges in our platform today. We will continue to enhance our infrastructure automation integrations, placement algorithms, application modeling and lifecycle management capabilities to help enterprises accelerate their adoption of Linux Containers.
Here is an interview by the Cube giving a good recap:
Sign Up for FREE on DCHQ.io Hosted PaaS (http://dchq.io) to get this template along with Ruby, Python, PHP, MEAN.JS, Clustered MongoDB, and many other template.
Published at DZone with permission of Amjad Afanah, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.