How to Break Through a Key Choke Point in Your Continuous Delivery Pipeline

DZone 's Guide to

How to Break Through a Key Choke Point in Your Continuous Delivery Pipeline

How not letting design evolve, unresolved CD tool issues, poor version control, and big data can choke up your continuous delivery pipeline.

· DevOps Zone ·
Free Resource

I just came across a really great article by Juni Mukherjee in Tech Bacon where she discusses five potential choke points which can prevent accelerated delivery through your continuous delivery pipeline and in fact slow it down or stop it completely. These include: not letting the design evolve, issues with CD tools, poor version-controlled infrastructure and issues with big data. But what naturally caught my eye was number 5, “You have an irrational fear of databases”.

Mukherjee proceeds to explain that for a while in CD, no one wanted to touch databases. But she argues that’s changing now. Mukherjee goes on to say that:

“Traditionally, database administrators were a specialized, siloed group who believed that databases couldn’t be continuously delivered. Databases are so complex, they said, that you need manual administration for objects, schema, and data. This is not true, but this mind-set has nonetheless caused expensive delays in some organizations.”

According to Mukherjee, with continuous delivery for the database tools like DBMaestro Teamwork, a whole host of benefits can be reaped such as security, scale and integration at an enterprise level, as well as a strong audit trail that helps with regulations.

Mukherjee really hits the nail right on the head! A 2015 study we conducted, determined that continuous delivery is strong and continues to grow. 67% of respondents claimed that they use CD for their application. This showed growth over previous surveys, and is remarkable considering that the concept of CD was only first described in a 2010 book co-authored by Jez Humble and David Farley. The need to increase productivity, achieve quicker time to market, and reduce risk are the top reasons why organizations are adopting CD.

But at the same time, mistrust of automation is holding back CD for database. When asked if they use continuous practices for their database changes, 34% answered in the affirmative. The largest group, 36%, cited mistrust in automation for the database as the number one barrier for adopting CD.

Download our wildly popular eBook, In Database Automation We Trust.

Leveraging database enforced change management and baseline aware deployments can make the difference and help combat mistrust. Ensuring all database changes are properly managed, safely deploying them with no risk of code over-rides, and being able to issue automation-stopping red-flags if needed will make the database a safe player in the continuous delivery process.

Ultimately, database professionals recognize that database continuous delivery is possible, and vitally important ad as enterprises continue to adopt CD for the database, the need to increase productivity and reduce time to market will drive more companies to implement CD in their database.

automation, continuous delivery, devops

Published at DZone with permission of Yaniv Yehuda , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}