Forget the gap between Dev and Ops - the gap between Devs and DBAs is a chasm. Here are some observations from the field about the causes of the rift and some ideas about how to close the gap (and even whether the gap is worth closing). Oh, and I'm writing a book about it.

5. Where is the
goddam
referential
integrity?!

6. Dev Prizes
for getting
through the
dba
defenses

7. Application is
one many
inputs to a
Smart store
of business
data:
consistent,
complete

8. Database
serves the
needs of the
application
(and the team)

9. iT’S A
TRAP!

10. What are we
looking for?

11. Rapid
Frequent
And safe
changes to
databases
that are:

12. More nimble, better
control of deployments

13. Avoid a data free-for-all

15. use the
Source (code)

16. All db scripts in
version control
use ci and tdd for
changes
Test in a
deployment pipeline

17. use the
(homomorphic)
force

18. Conway’s Law
We are “...constrained to
produce designs that are
copies of the
communication structures
of (the) organisation”

19. Designs that
match the
communication
structures

20. What about
microservices?

21. Beware of data
duplication with
separate
databases

22. Add a data
capability
to the
team?

23. Adopt new techniques:
cqrs, event sourcing, separate bi, data archiving,
eventual consistency and reconciliation,
actually talking to dbas...,

25. Free at
thedlmbook.com