Docker and Databases
summary
Claim: containers can host stateful databases reliably and speed workflows. Uses Docker, PostgreSQL, Docker Desktop/WSL and Docker Compose to demo three persistence modes: bind mounts, named volumes, data volume containers. Measured result: provisioning drops from 45–60 minutes to about 2 minutes, saving roughly a month of Dev time per year. Builds include a primary and replica Postgres pair using a base backup over a shared named volume and a Compose file; streaming replication comes up and serves queries in minutes.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker background
- 1:49Why run databases in Docker
- 5:21Options for persisting database data
- 10:15Demo: Bind mounts for PostgreSQL
- 13:23Demo: Named volumes for PostgreSQL
- 18:47Demo: Data volume containers
- 22:25Testing and practical use cases
- 23:49Demo: High availability setup
- 29:09Demo: Docker Compose for automation
- 34:49Cleanup and resources
- 35:33Q&A session
related talks
56mExperiments with Postgres in Docker and the Cloud
40mExperience on build Database Docker Desktop Extensions
30mDev and Test Agility for Your Database with Docker
47mFrom a Database in Container to DBaaS on Kubernetes
01h 00mData + Docker = Disconbobulating?
01h 06mPanel: Running Databases in Containers
25mAre Containers Ready for Production Databases?
35mContainerizing PostgreSQL and Making it Cloud Native Ready