Book Image

A Developer's Essential Guide to Docker Compose

By : Emmanouil Gkatziouras
Book Image

A Developer's Essential Guide to Docker Compose

By: Emmanouil Gkatziouras

Overview of this book

Software development is becoming increasingly complex due to the various software components used. Applications need to be packaged with software components to facilitate their operations, making it complicated to run them. With Docker Compose, a single command can set up your application and the needed dependencies. This book starts with an overview of Docker Compose and its usage and then shows how to create an application. You will also get to grips with the fundamentals of Docker volumes and network, along with Compose commands, their purpose, and use cases. Next, you will set up databases for daily usage using Compose and, leveraging Docker networking, you will establish communication between microservices. You will also run entire stacks locally on Compose, simulate production environments, and enhance CI/CD jobs using Docker Compose. Later chapters will show you how to benefit from Docker Compose for production deployments, provision infrastructure on public clouds such as AWS and Azure, and wrap up with Compose deployments on said infrastructure. By the end of this book, you will have learned how to effectively utilize Docker Compose for day-to-day development.
Table of Contents (19 chapters)
1
Part 1: Docker Compose 101
6
Part 2: Daily Development with Docker Compose
12
Part 3: Deployment with Docker Compose

Running your Compose application to an existing cluster

Previously, we managed to run a Compose application on ECS by using an ECS Docker context. By deploying the application, a new infrastructure was provisioned through CloudFormation and an entire new ECS cluster was created for the application.

If we take our time and check the CloudFormation file, we can see that various AWS components have been created:

  • A VPC and its subnets
  • A CloudWatch log group
  • Security groups
  • A load balancer
  • CloudMap for service discovery
  • An ECS cluster
  • ECS tasks

By default, CloudFormation will use the default VPC and subnets that already exist in our AWS account. The load balancer, security groups, and CloudMap, which assist with service discovery, will have to be created, as well as the ECS cluster and the ECS tasks. Those applications will be deployed to AWS Fargate.

It is obvious that these resources are provisioned and we have no control over their settings...