Apcera's POV on Containers
Apcera's POV on Containers
Here's one CSO's thoughts on the state of containers and the belief that a support framework of capabilities is needed to successfully implement a container strategy.
Join the DZone community and get the full member experience.Join For Free
Learn how to migrate and modernize stateless applications and run them in a Kubernetes cluster.
Thanks to Mark Thiele, Chief Strategy Officer at Apcera for sharing his thoughts on the state of orchestration and deployment of containers for DZone’s upcoming Containers Research Guide that will be published in early-August.
Q: How is your company involved in the orchestration and deployment of containers?
A: Container management platform for cloud-native and legacy apps.
Q: What do you see as the most important elements of orchestrating and deploying containers?
A: It goes well beyond orchestrating and deploying. We believe a support framework of capabilities is needed which includes: networking, storage, orchestration/scheduling, lifecycle management, audit patch management, security, deployment, automation, bursting, monitoring, log aggregation, routing, load balancing, and firewalls. We allow the customer to define the requirements of their containers and add capacity. We provide a container ecosystem.
Q: Which programming languages, frameworks, and tools do you, or your company use, to orchestrate and deploy containers?
A: Built-in stages for multiple languages (e.g. Ruby, Java, Go, PERL, PHP, Python) and service integration, creation, and management.
Q: How has the orchestration and deployment of containers changed application development?
A: Decreased the time to opportunity or value. Application developers don’t have to ask for cloud capacity. They can create an iteration and run in small bits without large workloads. Individual VMs would overwhelm a Mac or PC.
Q: What kind of security techniques and tools do you find most effective for orchestrating and deploying containers?
A: We can’t protect against application threats but we do reduce the opportunity for risk by only rolling out what’s supposed to roll out based on predetermined security protocols. We ensure the product is as protected to the standards as it can be. A developer cannot take a container and put it into production. The deployment systems catch and evaluate against predefined standards.
Q: What are some real-world problems being solved by the orchestration and deployment of containers?
A: We helped one smaller client remove 14 load balancers among other infrastructure cost and resource savings. While some customers use us for containers, most are using us to reduce their workload environment by 85%. We can wrap complex infrastructure legacy apps (e.g., SAP) in containers and release into production in minutes with automatic updates. We give IT departments back the time to be innovative. We lower risk through automation and provide greater flexibility to deliver versus business objectives.
Q: What are the most common issues you see affecting the orchestration and deployment of containers?
A: 1) Lack of corporate/enterprise vision to get through the noise in the IT space. 2) Every company has a large number of critical apps in the cloud. They’re concerned with cloud lock-in. They have analysis paralysis trying to prevent themselves from getting painted into a corner. We give the customer the opportunity to use IT as a resource – use the right resource at the right time.
Q: Do you have any concerns regarding the current state of orchestrating and deploying containers?
A: Noise and misinformation.
Q: What’s the future for containers from your point of view - where do the greatest opportunities lie?
A: Yet to be discovered for the enterprise. Google has done a great job with their infrastructure. How will apps be designed to make the best use of containers? The savings and scale offered by containers are needed to keep up with demand over the next five years.
Q: What do developers need to keep in mind when working on orchestrating and deploying containers?
A: Be concerned with how to deploy and how to keep track of containers. Containers have simplified development and deployment.
Q: What have I failed to ask you that you think we need to consider with regards to containers?
A: When will we have active penetration capable of testing containers in real time?
Opinions expressed by DZone contributors are their own.