Craig Mullins

President & Principal Consultant, Mullins Consulting

“Application and database changes must be tightly coupled and orchestrated in tandem for successful DevOps.”

“As the continuous delivery model for applications gains momentum and acceptance, a tighter integration between application and database change will be required. Many application changes rely on changes to database structures, whether new columns, adjustment to data type and size, or even indexes for performance. These changes should be tightly coupled to the application changes that drive them. This should include delivering the changes, but also backing them out in the instances when that is necessary. This is more difficult than it may, at first, seem because some database changes are complex requiring structures, authorizations and data to be dropped and recreated. Automation of all of these steps - and integration with the application changes - is imperative for successful DevOps.”

IBM's take

The continuous delivery model brings a host of interesting new challenges. For example, if the new version of an application demands structural changes to an existing database, how do you roll out all these changes seamlessly? One approach is automating the various steps it takes to make database changes.

Call us at 1-866-261-3023 | Priority code: IBM Z

Visit us:

Visit us: