Skip to content

Instantly share code, notes, and snippets.

Last active March 5, 2021 09:01
What would you like to do?
DevOps Flow Series, part 3 of 4
Solving the dev database problem with GitHub, Docker and dbaclone
DevOps promotes self-service access to usable, production-like dev/test
environments – but so many data folks are encumbered with shared
development databases which are often inconsistent with production. It’s
difficult to isolate the development of different features, so they are
rolled together into big releases. It’s no wonder database deployments
are often expensive, complicated and risky.
What if it was possible for developers to provision themselves a
disposable, masked copy of last night’s production 64 TB database on
their regular workstation, with limited storage, in a matter of seconds?
What if it was as easy as “git clone f5”?
In this session attendees will learn to use GitHub, Docker, SSDT and
dbaclone to unshackle themselves from “Wild West” dev databases
and empower them to use modern branching techniques and Azure DevOps to
continuously deliver their updates to production.
The result? Empowered developers who can deliver value in smaller
batches, through significantly more regular and reliable deployments,
delivering value to users much more quickly.
More from the DevOps Flow series:
1. DevOps 101 for Data Folks:
2. Simple database deployments with GitHub, Azure DevOps Services and SSDT:
3. Solving the dev database problem with GitHub, Docker and dbaclone:
4. Zero downtime database deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment