Technical operations teams are justifiably skeptical about new technology platforms such as containers. They are usually most concerned about hardening for security and reliability because they exist to keep enterprise applications up and running securely. At the same time, product owners within their organizations need to deliver better, often more complex, software faster. Yes, the business landscape has changed profoundly; in today's business world, software is not only used to achieve competitive advantage, it is the business and provides the frontline customer experience.

Subsequently, significant pressure is mounting to accelerate the software pipeline in nearly every organization. This section briefly explains the roots of containers and why their benefits (a secure and fast software pipeline) have driven such a...

Using containers and orchestrators changes the way we look at building software and defining a software delivery pipeline. Container-based development fundamentally supports what the DevOps folks call a shift left, where developers of distributed systems become more accountable for the quality of the overall solution, meaning the binaries and how they are connected. Hence, wiring up my services in no longer the networking, integration, or operations teams' problem; it belongs to the developers. In fact, the YAML specification for connecting and deploying their application is now an artifact that gets checked into source code control! 

Faster deployment of fixes and enhancements is a prime motivation for containerizing monolithic web applications built with job and .NET. Containerization allows each team to operate...

Containers add some great new possibilities when approaching your enterprise application strategy, primarily with respect to cloud migration and application modernization. Containers allow organizations to elevate this conversation from the tactics around cloud migration and application stacks to a common application platform where virtually any application stack runs more efficiently while at the same time making the applications cloud-portable. 

What if, before you started migrating all of your applications to a specific cloud-specific provider, you instead containerize your applications first and then migrate them to the...

In April of 2018, Docker Enterprise 2.0 was a release. In this release, Docker added support for Kubernetes. Not some wrapped or repackaged version, but the real open source version. The advantage of running Kubernetes on Docker Enterprise 2.0 is simplicity. With Docker Enterprise 2.0, the universal control plane includes pre-installed Kubernetes, which runs alongside Swarm. This means that enterprises do not need to choose between Kubernetes and Swarm; they can have them both. This is a big deal for organizations that need to deal with both pockets of advanced microservice applications and simpler n-tier traditional applications. With Docker Enterprise 2.0, microservice teams are free get their Kube on, while the rest of the teams get up to speed with Swarm. Also, it allows an enterprise to handle a more manageable learning curve...

In the last 5 years, containers have come out of obscurity and into the spotlight across the software industry and DevOps. The profound organizational impact of containers spans software developers, IT admins, DevOps engineers, architects, and executives alike. From the beginning, Docker, Inc. has been at the center of the container movement and remains committed to the long term success by supporting industry standards, the open source community, and most recently enterprise customers with a Kubernetes-capable Docker Enterprise 2. 

In the next 5 years, the enterprise adoption of containers will blossom. Subsequently, most organizations will begin looking for an enterprise-grade solution that balances cost and security with speed and leading-edge platform features. Docker Enterprise's single pane of glass for hybrid cloud and on-premises clusters, along...

1. How long have containers been around?
2. What is Docker, Inc. and what does it do?
3. What is the difference between Docker Engine-Community and Docker Enterprise?
4. What is the difference between Docker and Kubernetes?
5. What is the best orchestrator for deploying simple n-tier web applications?
6. How does Docker support Kubernetes?
7. How does container-based development impact application developers? 
8. Why would I need fewer cloud admins with a cloud-first strategy?

• Docker Enterprise production information:
  • https://www.docker.com/products/docker-enterprise
  • https://docs.docker.com/ee/
• Docker Enterprise FIPS compliance:
  • https://blog.docker.com/2017/06/docker-ee-is-now-in-process-for-fips-140-2/
  • https://docs.docker.com/compliance/nist/fips140_2/