►
From YouTube: Lightning Talk: Continuous Delivery…except for Database Changes - Robert Reeves, Liquibase
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
Lightning Talk: Continuous Delivery…except for Database Changes - Robert Reeves, Liquibase
JW Grand Ballroom 4
Speakers: Robert Reeves
Too often, when we speak of continuous delivery, we omit database changes. Those are handled by another team, another process. As we continue accelerating application releases, the pain of database change delivery becomes more acute. Robert will discuss how we got into this mess and how we should embrace our database friends to bring them to the DevOps party.
A
So
let's
go
to
the
next
slide,
normally
the
little
space
bar
kind
of
works,
but
we'll
have
to
do
this
all
right.
So
look.
I'm
robert
co-founder
cto
over
at
a
company
called
liquibase.
We
do
database
schema
management.
Probably
why
I'm
talking
about
this
today?
If
you
want
to
get
me
to
shut
up,
you
can
ask
me
my
thoughts
about
the
new
black
adam
trailer
that
dropped
today
or
asked
me
to
explain
doctor
strange
multiverse
of
madness.
A
I
will
go
on
for
hours,
I'm
also
one
of
those
lucky
clowns
that
got
into
austin
in
the
90s.
Thank
you
for
coming
to
visit.
I
appreciate
it.
If
you
see
me
out
tonight,
ask
me
to
buy
you
a
drink
because
you
had
to
get
on
a
plane,
and
I
didn't.
I
owe
you
thank
you,
but
larry
wall,
the
guy
who
started
perl.
A
He
said
there
were
three
qualities
of
a
good
software
engineer,
laziness,
impatience
and
hubris,
and
I
have
them
all.
I
started
out
as
a
software
configuration
manager
back
in
the
day
and
I'm
dating
myself
showing
how
old
I
am
that
was
take
code
from
dev
to
test
to
production,
dropping
things
along
the
way.
Eventually
we
changed
that
into
devops
all
that
other
stuff,
but
my
job
was
to
automate
myself
out
of
a
job
right.
That
was
my
job.
A
What
I
told
myself,
because
I
wanted
to
go
to
the
lake
I
wanted
to
go
and
party
down,
I
didn't
want
to
hang
out
in
front
of
a
computer
screen
and
it
was
great
and
good
news.
Everyone
we've
automated
the
application,
but
but
I
think
we
forgot
something
right.
We
forgot
something
along
the
way
we
forgot
to
bring
our
friends
over
and
share
data
services.
We
forgot
to
bring
our
friends
over
there.
We
let
them
take
care
of
this.
We
don't
want
to
deal
with
this
now.
A
B
A
A
We
wanted
the
world's
best
fastest
computer
to
review
every
single
thing
that
was
changing
on
that
database,
because
the
risk
of
something
going
wrong
was
too
great.
Data
is
the
most
valuable
asset
the
company
has.
It
is
all
right,
ask
any
bank,
it
is
the
most
important
thing
and
we
can't
afford
anything
to
happen
to
it.
But
then
this
whole
agile,
cd,
devops
microservices
cloud
native
thing
happened,
and
now
we
can't
afford
to
go
slow.
A
What
do
we
do?
What
do
we
do
all
right?
So
let
me
use
an
analogy
here
who
here
knows
that
you
cannot
pump
your
gas
in
new
jersey,
okay,
all
right.
Who
knows
why
cool
I'll
tell
you
all
right.
So
in
the
40s
there
was
a
gas
station
owner
who
said
I'm
going
to
give
you
a
discount
if
you
pump
your
own
gas
now
I
don't
know,
maybe
this
person
wouldn't
sit
on
a
rocking
chair
and
whittle
sounds
great
now.
What
did
all
the
other
gas
station
owners
do?
Did
they
compete
on
services
and
pricing?
A
Did
they
offer
the
same
discount?
Did
they
have
more?
You
know
oil
changes
or
things
like
that?
Did
they
give
you
a
puppy
with
a
full
tank
of
gas?
No,
what
they
did
is
they
formed
an
industry
consortium
and
lobbied.
The
new
jersey
state
legislature
to
pass
a
law
saying
was
illegal
pump,
yarn
gas
now.
Do
we
imagine
that
there
are
far
fewer
gas
station
mishaps
in
new
jersey
than
in
the
rest
of
the
nation?
A
A
A
lot
of
great
stuff
was
happening
that
year
now,
let
me
tell
you
this
guy
did
not
put
out
a
bad
album
this
one,
my
favorite
all
right,
there's
a
reason
why
it
gets
sampled
got
sampled
by
so
many
hip-hop
artists
during
the
80s
amazing.
All
right.
We
have
the
beginnings
of
new
cinema
a
movie
about
divorce.
Oh
my
god
scandalous!
A
Some
of
you
might
remember
this
from
guardians
of
the
galaxy
some
of
you
might
have
had
one
of
these
all
right,
wow,
pretty
cool
and
some
people
with
really
large
collars
came
out
with
a
database
and
at
the
time
1979
first
release
of
oracle
first
customer
cia.
Then
they
sold
it
through
just
just
all
fortune
500..
A
Now,
if
you
wanted
to
find
out
who
your
top
10
customers
were
by
revenue
in
the
greater
tri-state
area,
you
had
to
get
a
room
about
this
big
with
a
bunch
of
paper
and
people
and
chalkboards
and
figure
this
out,
and
I
guarantee
you'd
be
wrong,
but
in
seconds
you
could
figure
this
out
with
a
database
amazing
and
we
used
sql
files
and
it
had
tables-
and
you
know
not-
a
lot
has
changed
since
then.
All
right,
not
a
lot
all
right,
great
we're
running
the
database
in
somebody
else's
server
in
the
cloud.
A
Okay,
but
not
much,
I
mean
our
the
way.
We're
managing
these
things
has
not
changed.
We
have
all
sorts
of
great
things
for
the
application
side
of
the
house,
but
what
the
hell
are
we
doing
for
our
dbas,
the
most
important
asset,
the
company
has,
what
are
we
doing
very
little,
and
so,
as
we
get
to
these
new
wonderful
things
that
we're
doing
over
on
the
app
side
of
the
house,
what
we're
doing
is
we're
going
to
dbas
and
saying
congratulations.
A
D
C
A
A
We've
got
to
be
more
inclusive
here,
and
so
let's
talk
about
what's
in
it
for
you,
so
our
friends
over
at
dora,
it's
not
google
cloud,
it's
all
complicated.
So
so
dr
forsgren's
folks,
all
right
state
of
devos
report.
They
did
one
last
year,
we're
gonna
do
one
this
year
and
the
thing
that
really
jumped
out
at
me
this
year
was
they
started,
studying
database
change
management
and
what
they
found
is
they
found
that
elite
performers
were
3.4
times
more
likely
than
their
lower
performing
peers
to
have
database
change
management
boy?
A
Is
that
really
fuzzy?
I
don't
know
what
is
database
change
management?
Okay?
Well,
they
just
said
database
change
management,
that's
what
they
asked
in
the
survey
cool
now
3.4.
What
does
this
mean
great
thanks?
Robert
appreciate
it
well
number
one
on
their
list
at
3.8
was
good
documentation
and
if
you
had
a
chance
to
see
ember's
presentation
yesterday
here
it
was
awesome.
A
3.4
is
database
next
after
that,
there's
a
steep
drop-off
in
the
twos
for
everything
else.
So
my
challenge
to
you
bring
a
dba,
bring
a
dba
to
the
party
all
right
next
time
you
come
to
event
next
time.
You
are
doing
something
you
are
trying
to
improve
your
process.
Bring
a
dba
to
the
party.
Just
have
them
hang
out
invite
him
to
the
meeting.
It's
easy!
That's
all
you
got
to
do.