Book Image

Mastering Docker Enterprise

By : Mark Panthofer
Book Image

Mastering Docker Enterprise

By: Mark Panthofer

Overview of this book

While known mostly as the open source engine behind tens of millions of server nodes, Docker also offers commercially supported enterprise tooling known as the Docker Enterprise. This platform leverages the deep roots from Docker Engine - Community (formerly Docker CE) and Kubernetes, but adds support and tooling to efficiently operate a secure container platform at scale. With hundreds of enterprises on board, best practices and adoption patterns are emerging rapidly. These learning points can be used to inform adopters and help manage the enterprise transformation associated with enterprise container adoption. This book starts by explaining the case for Docker Enterprise, as well as its structure and reference architecture. From there, we progress through the PoC,pilot and production stages as a working model for adoption, evolving the platform’s design and configuration for each stage and using detailed application examples along the way to clarify and demonstrate important concepts.The book concludes with Docker’s impact on other emerging software technologies, such as Blockchain and Serverless computing. By the end of this book, you’ll have a better understanding of what it takes to get your enterprise up and running with Docker Enterprise and beyond.
Table of Contents (17 chapters)
Free Chapter
1
Section 1: Getting Started with Docker Enterprise
5
Section 2: Piloting Docker Enterprise
10
Section 3: In Production with Docker Enterprise

First Application in Production with Docker Enterprise

Getting your first application ready for production and preparing a production cluster for its live debut is an important step in the container-adoption process. This is where we see rookie mistakes damage the reputation of very smart technologists. In one case, without running High Availability (HA) for non-production, the customer built their first HA cluster for production, not practicing with the non-production cluster first and did it with just two managers nodes. Had they started in non-production the failure would have been much less visible (remember, an even numbers of managers means trouble)! Some key lessons learned here were to keep your non-production and production cluster architectures very similar and always try new things in the non-production cluster first.

In this chapter, we will look at important topics...