Book Image

Docker Certified Associate (DCA): Exam Guide

By : Francisco Javier Ramírez Urea
Book Image

Docker Certified Associate (DCA): Exam Guide

By: Francisco Javier Ramírez Urea

Overview of this book

Developers have changed their deployment artifacts from application binaries to container images, and they now need to build container-based applications as containers are part of their new development workflow. This Docker book is designed to help you learn about the management and administrative tasks of the Containers as a Service (CaaS) platform. The book starts by getting you up and running with the key concepts of containers and microservices. You'll then cover different orchestration strategies and environments, along with exploring the Docker Enterprise platform. As you advance, the book will show you how to deploy secure, production-ready, container-based applications in Docker Enterprise environments. Later, you'll delve into each Docker Enterprise component and learn all about CaaS management. Throughout the book, you'll encounter important exam-specific topics, along with sample questions and detailed answers that will help you prepare effectively for the exam. By the end of this Docker containers book, you'll have learned how to efficiently deploy and manage container-based environments in production, and you will have the skills and knowledge you need to pass the DCA exam.
Table of Contents (22 chapters)
1
Section 1 - Key Container Concepts
8
Section 2 - Container Orchestration
12
Section 3 - Docker Enterprise
17
Section 4 - Preparing for the Docker Certified Associate Exam

Scaling and updating application components

Orchestrators provide another great feature. If my application is prepared to run more than one instance of some components, the orchestrator will help us easily manage this replication. This is easy because components are based on containers, so if we need to run more than one replica of a component, we can ask the orchestrator to execute more containers. In fact, this feature is key because, in orchestration, we define an application component with the number of required healthy replicas. If all required replicas are alive, that application component will be healthy. If one replica dies, a new one will be executed to ensure that the required number is accomplished.

The management of replicas is one of the features provided by orchestrators. If application performance is compromised and application logic allows replication, we will be able to scale up or down the number of replicas or instances of a component.

On the other hand, we learned...