Where is the goddam
referential integrity?!
Dev Prizes for getting through the
dba defenses
Application is one many
inputs to a Smart store of business
data: consistent, complete
Database serves the
needs of the application
(and the team)
iT’S A TRAP!
What are we looking for?
RapidFrequentAnd safe
changes to databases that are:
More nimble, better control of deployments
Avoid a data free-for-all
use the Source (code)
All db scripts in version control
use ci and tdd for changes
Test in a deployment pipeline
use the (homomorphic)
force
Conway’s LawWe are “...constrained to produce designs that are
copies of the communication structures
of (the) organisation”
Designs that match the
communication structures
What about microservices?
Beware of data duplication with separate databases
Add a data capability to the team?
Adopt new techniques: cqrs, event sourcing, separate bi, data archiving, eventual consistency and reconciliation, actually talking to dbas...,
Free at thedlmbook.com