• Continuous integration is a no-brainer. JFDI.

    Continuous deployment makes me nervous from a DBA perspective.

    If a deployment means a change to a big table and replication is involved then it gives me the screaming willies.

    Where there are small changes to the DB I'm much less worried. It all depends on what the change might be and therein lies the rub.

    There is also consideration for the data rollback strategy.

    How does a team of developers decide where on the spectrum of worry the deployment will put the DBA?

    Ideally I'd like to be able to support continuous delivery with the caveats mentioned earlier.

    I don't think a Continuous Delivery for non-data deployments is conducive to a good developer/DBA relationship. No matter how legitemate DBAs will be seen as blockers not guardians.

    In terms of non-DB developers continous delivery eliminates a layer of bureaucracy. Frankly the traditional release process is stressful. I've seen a project manager in tears when facing a remedial release. Sometimes project managers need a hug:ermm: