dbaclone_Abstract.txt

DevOps Flow Series, part 3 of 4

Title:
Solving the dev database problem with GitHub, Docker and dbaclone

Abstract:
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:
   https://gist.github.com/Alex-Yates/efef91357c6bd0dc1fbe63f2eb464f68
2. Simple database deployments with GitHub, Azure DevOps Services and SSDT: 
   https://gist.github.com/Alex-Yates/43c7f4d51a651cd8b3dcdcb48843691f
3. Solving the dev database problem with GitHub, Docker and dbaclone:
   https://gist.github.com/Alex-Yates/8125be587e58863ad35e0845ab6ffd5a
4. Zero downtime database deployments
   https://gist.github.com/Alex-Yates/ac4c791bbd98eb3269f35db59cc30f88