continuous delivery & the database- the final frontier

Continuous Delivery & the Database - The Final Frontier

Feb 2015

2 Copyright 2015. Confidential – Distribution prohibited without permission

Before We Begin

▪ You will be on mute for the duration of the event

▪ Please type a message in the Questions box in the

Control Panel if you can’t hear us (please check

your speakers and GoToWebinar audio settings

first)

▪ If you have questions during the session, please

submit them on the Q&A bar on your GoToWebinar

dashboard and we will address them at the end

▪ A recording of the full webinar will be put up online


Agenda

▪ Continuous Delivery is coming

▪ What about the database?

▪ Introducing DBmaestro

▪ Introducing XebiaLabs’ XL Deploy & XL Release

▪ How DBmaestro, XL Deploy & XL Release work

together

▪ Q&A


Presenters

Yaniv Yehuda

CTO, Co-Founder at DBmaestro

Yaniv spent the last years raising awareness about the challenges

around database development and deployment, and how to

support database Continuous Delivery.


About DBmaestro

▪ The leading provider of DevOps for Database

▪ Enables control of database development and deployment


Presenters

Andrew Phillips

VP Products for XebiaLabs

▪ Lots of enterprise software development on high-performance

systems

▪ Been on both sides of the “Dev…Ops” fence

▪ Active open source contributor and committer

▪ Regular meetup, conference etc. presenter


About XebiaLabs

▪ We build software to support DevOps and Continuous Delivery at scale…

▪ …to accelerate your Business


DevOps & CD: a must for every company

▪ Every business is an IT business

▪ Customers demand that you deliver new features faster

▪ If you don’t, your competitor probably will


DevOps & CD: a must for every company

Adopters:

Ship code40x faster

Complete thosedeployments60x faster

than their peers.

Have 95% fewer failures

and rollbacks

DevOps

ContinuousDelivery

Time to Market


Continuous Delivery moving ahead!

▪ Recently Conducted DBmaestro Survey

− Over 150 companies

− Over 200 participants


What does this mean for you?

▪ Need to move towards architectures and processes that

allow changes to be made quickly and regularly

▪ But can’t afford to break things badly!

▪ Adoption of Continuous Delivery pipelines becoming more

and more well-established



▪ Need to move towards architectures and processes that

allow changes to be made quickly and regularly

▪ But can’t afford to break things badly!

▪ Adoption of Continuous Delivery pipelines becoming more

and more well-established

▪ Are you doing CD for the entire application?



▪ Many organizations only consider the application code when

talking about CD pipelines

▪ Uses established practices in packaging, verifying and

deploying new code and promoting changes from one

environment to the next



▪ Many organizations only consider the application code when

talking about CD pipelines

▪ Uses established practices in packaging, verifying and

deploying new code and promoting changes from one

environment to the next

▪ But what about your database?


What about the database?

▪ Why?


CD for the database

▪ In many organizations, changes to databases are not

included in the CD picture

▪ Too much risk

▪ Too little awareness of the packaging, deployment,

promotion etc. concepts used for application code

▪ Insufficient tool support for these concepts


CD for the database

▪ If you don’t include databases changes in the overall

deliverable, your CD pipeline can get stuck pretty quickly!

▪ The DB is essential from a business and compliance point

of view

▪ Should be your strongest link!


So why not move forward?

▪ Mistrust…


What is the problem?

▪ Root Causes for issues:

− Challenging manual version control process

− Static deployments code overrides

− Dynamic deployments unaware of version control

− No release automation red-flags – don’t know when to stop the line…

20 Copyright 2015. Confidential – Distribution prohibited without permission 20

Version Control Process

(file based)

Development Process

Check-Out Script

Modify Script

Get updated Script from DB

Check-In Script

Compile Scriptin DB

Debug Scriptin DB

?

??

?

A

A’

Two isolated processes


Scripts & version control

▪Challenges:

− Code-overrides

− Working on the wrong revisions

− Scripts do not always find their way to the version control solution

− Out of process updates go unnoticed

− Hard to locate outdated update scripts

▪ Playing safe? What we really need:

− The actual code of the object

− The upgrade script

− A roll-back script

▪ Scripts

− Hard to test in their entirely (holistically)

− Hard to test due to colliding dependencies

− Need to run in a specific order…

− Much harder to deal with project scope changes


X1.11.1.11.11.21.31.41.51.61.7

Scripts… build once deploy many

Int QA Stage Prod

Database Deploy Script

Environment

Re-Base (due to defects)

Dev

Dev

Dev

Model

1.1 1.2

1.2 1.3

1.3 1.4

1.4 1.5

1.5 1.6

1.6 1.7

1.11.11.41.7

1.1 1.2

1.2 1.3

1.3 1.4

1.4 1.5

1.5 1.6

1.6 1.7

1.1 1.2

1.2 1.3

1.3 1.4

1.4 1.5

1.5 1.6

1.6 1.7

Out of Process Change

X

X

X

X

X

? 1.1.1

X


Scripts are static…

▪ Scripts, unless super sophisticated:

− Unaware of changes made in the target environment

− Time passed from their coding to the time they are run

− Potentially overriding production hot-fixes or work done in parallel by another team

▪ Content changes are very hard to manage

− Metadata & lookup content does not practically fit into the VC

− In most cases they are simply not managed


Version control: one enforced process


Dealing with challenges…

▪Integrated Database Version Control process

− Leverage proven version control best practices

• Forcing check in & out for changes

• Labels

• etc..

− No code-overrides

− Always working with the correct revision

− All changes are documented

− Always know who did what, when, why and from where

− No out-of-process changes

− Supporting structure, code and content

▪ No time spent on manual coding of the change scripts


Build & deploy on demand

1.11.21.31.41.51.61.7

*

Int QA Stage Prod

Database Deploy Script

Environment* Execute the same script being

executed at the Stage environment

Re-Base (due to defects)

DevDev

DevModel

1.1 1.2

1.2 1.3

1.3 1.4

1.4 1.5

1.5 1.6

1.6 1.7

1.1 1.4

1.4 1.7

1.1.1 1.7

1.1 1.1 1.11.41.7

File Based Version Control

Out of Process Change

1.1.11.7 1.1.11.7


Using tools

Test cases using compare & sync tools:

An index exists in source (QA) but not in target (Production)

What should we do? Add the index or not?


Compare & sync tools

Safe to automate?

No. Requires manual inspection…


Why break production???

A compare & sync tool:

▪ Is unaware of any changes that occurred before the time it ran

▪ Has no knowledge of changes that took place at the target environment

▪ Does not leverage version control for more information

▪ Unable to deal with conflicts & merges between different teams

▪ Requires manual inspection

▪ Requires detailed knowledge regarding each change as part of the process

Mistrust AGAIN…

So…no automation… as we fear automating problems into

production and a major risk!!!


Safety net

Static script based deployment


Deploying changes if needed

Development Baseline

Previous Label /

Production Golden Copy

Production

If we had the index in the baseline =>

we should take it down from production…

(Deploy Change)


Or protecting target environment…

Development Baseline

Previous Label /

Production Golden Copy

Production

BUT… If no index in baseline =>

we should protect the NEW index on production!!!

(Protect Target)


Dealing with conflicts => merging changes


What does DBmaestro offer?

▪ Database Enforced Change Management solution

+ Database version control

+ Enforce best practices

+ Plugs into the ALM (change request, tickets & work items)

+ Database merge & change impact analysis

+ Know who can do what, where, when & why

▪ DevOps Solution for databases

+ Baseline aware deployment automation, rollback & recovery

+ Reduce database deployment issues

+ Plugs into release management & Continuous Delivery

Allows you to package, verify, deploy and promote database changes just as you would do with application code…

putting you in a position to build a full delivery pipeline…


What does XL Deploy offer?

▪ Deployment Automation tool

▪ “Gets application X running in environment Y automatically”



▪ Package the deployment of database changes along with all your other

application components to give a unified picture

▪ Easily promote the same package (including database changes!) from one

environment to the next, handling environment-specific differences automatically


What does XL Release offer?

▪ Release/pipeline orchestration tool for Continuous Delivery

▪ “Describe, execute and improve all the steps required to get your apps from development to

production”



▪ Define the entire dev-to-prod pipeline/release process to take into

account your current risk/comfort level for automated database

changes

▪ Invoke XL Deploy or DBmaestro directly to apply database changes

automatically

▪ Or add manual impact analysis/review gates if you require or prefer

additional checks



▪ Also plan & execute additional database actions such as backups,

copies etc.

▪ Easily tweak your process over time as your CD situation changes


How do DBMaestro, XL Deploy & XL Release work together?

▪ You need to be able to package, deploy and promote database

changes just like other application code to fully do CD

▪ The combination of DBmaestro, XL Deploy & XL Release allows you

to do just that


How DBmaestro, XL Deploy & XL Release work together?

▪ DBmaestro & XL Deploy: include database changes alongside your

code to give you a unified view and automation setup for deployments

▪ DBmaestro & XL Release: Define your delivery pipeline – including

the database – to give you exactly the level of automation and manual

validation that works for you by


Useful resources

▪ Get started today!

www.xebialabs.com

www.xebialabs.com/products

▪ Stay informed:

blog.xebialabs.com

@XebiaLabs

youtube.com/xebialabs

▪ Get started today!

www.DBmaestro.com

http://www.dbmaestro.com/products

▪ Stay informed:

dbmaestro.com/blog/

@dbMaestro

youtube.com/DBmaestro

http://www.xebialabs.com/

http://www.xebialabs.com/trial

http://blog.xebialabs.com/

http://twitter.com/xebialabs

http://youtube.com/xebialabs

http://www.dbmaestro.com/

http://www.dbmaestro.com/products-solutions/all-about-teamwork/

http://www.dbmaestro.com/blog/

http://twitter.com/dbMaestro

https://www.youtube.com/user/dbMaestroDemo


Thank you!

Q & A

continuous delivery & the database- the final frontier

Technology

confidential distribution

permission devops cd

database continuous

xl releasehow dbmaestro

dbmaestro yaniv

dbmaestro surveyover

xl release work togetherqa

questions box