Composing your Containerized Microservices
summary
Explains how Docker Compose actually builds a multi-container setup: a MariaDB container, a Java user service built from a Dockerfile, and Liquibase migrations wired with a wait-for-it script so migrations run after the DB is ready. Uses named network + internal DNS and a shared volume as a file-semaphore to order startup; shows ports kept internal (no host publish). Demonstrations run locally and also show Compose targeting Minikube and ECS, with practical gotchas and working solutions.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 5:39What is Docker Compose
- 11:20Setting up a database with Compose
- 20:30Managing database state and migrations
- 31:38Handling service dependencies
- 41:04Advanced Compose features
- 47:17Deploying Compose to production
related talks
30mSimplify All the Things with Docker Compose
28mMulti-Container Applications with Docker Compose
51mJava-based microservices, containers, Kubernetes - how to
44mDocker and the Path to a Better Staging Environment
30mIntegration tests & testContainers
49mDocker Compose: From Localhost to the Cloud
02h 40mDocker Compose 101
39mDocker and the Path to a Better Staging Environment