Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Additional Considerations for Containers

DZone's Guide to

Additional Considerations for Containers

In the last segment of our interviews with various IT industry professionals, we asked them what they had left to say. Here's what they gave us.

· Cloud Zone ·
Free Resource

Site24x7 - Full stack It Infrastructure Monitoring from the cloud. Sign up for free trial.

To gather insights on the current and future state of containers, we talked to executives from 26 companies. We asked, "What have I failed to ask you that you think we need to consider with regards to containers?" Here's what they told us:

Cost

  • Why are people choosing K8 over Docker when deploying legacy applications? K8 is a square peg, legacy apps require a round hole. The choice of deploying Docker Swarm versus K8 seems to be driven by IT development teams, without any real thought of the ongoing cost to maintain/manage. 
  • Need to think about cost of ownership, management, knowledge transfer, how to prepare developers to adopt. Keep up with what’s going on. Serverless is obvious automation of container technology. Ultimately a business problem to be able to show the value containers are providing. 
  • We see a lot of companies and developers diving into containers without thinking about cost and technical debt over the long term. There’s not the same focus on cost, consequences, tradeoffs, and ROI.

Growth

  • Containers won’t plateau for another three years. We’ll see others (i.e., IBM) get involved. 
  • Ramping and speeding up. Help communities to decrease risks and threats.

Security

  • Containers are a huge change for enterprise deployment of applications. They involve application development, CI/CD pipeline automation, private-public cloud deployments, container scheduling, deployment, and management. Security challenges exist at multiple stages during this new process. That’s why people are talking about DevSecOps, DevOpsSecs, etc. By leveraging this modern automated container process, security solutions can be integrated into the DevOps chain at multiple stages for the first time. New security technologies are required that use traditional security techniques like network firewalling and endpoint security. For the first time, security can be automated and provide protection against multiple threat vectors, and the traditional boundaries between network security, host security, vulnerability management, endpoint security and authentication/authorization are being blurred. This is the problem we’re trying to solve at NeuVector – providing a multi-vector security solution designed for the new container environment. 
  • Security is not already taken care of. You need to actively consider security on a continuous basis.

Other

  • Broad platform issues take data and features into consideration.

  • Be able to programmatically perform on and off schedulers. If stateful and stateless, how are you managing K8 and understanding the health around all of them – the cluster itself and the connection with each other.
  • What technologies will be made obsolete by containers? Specifically -what’s the future for VMs in a container world?
  • What’s next after containers - functions?
  • What areas of business currently use containers?
  • With all of the frameworks and automation layers, where are companies able to create differentiated value?

Here’s who we spoke to:

Site24x7 - Full stack It Infrastructure Monitoring from the cloud. Sign up for free trial.

Topics:
containers ,cloud ,interview ,industry professionals ,cloud cost analysis ,cloud security

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}