Recently, the Agile Austin DevOps SIG invited Datical to talk about the
impact of DevOps practices on database change management. This was a great
opportunity for us to talk to folks about our approach to managing
application schema change in IT organizations that have moved or are moving
to more responsive and agile planning, development, and delivery processes.
It was a lively discussion with some great feedback from the audience.
In framing the discussion, I relied heavily on "The Three Ways" of DevOps.
The Three Ways are the principles that underpin the DevOps patterns that Gene
Kim discusses in detail in his novel "The Phoenix Project" and in the"The
DevOps Cookbook", written by John Allspaw, Patrick Debois, Damon Ewards, Jez
Humble, Kim, Mike Orzen, & John Willis. Here's a quick summary of The Three
The First Way: Systems Thinking - This Way stresses... (more)
In the third post in this series, I’d like to talk about the Second Way of
DevOps: Amplifying Feedback Loops. Here’s a refresher on The Second Way
from my introductory post in this series:
The Second Way: Amplify Feedback Loops – This Way deals primarily with
facilitating easier and faster communication between all individuals in a
DevOps organization. The goals of this step are to foster better
understanding of all internal and external customers in the process and to
develop an accessible body of knowledge to replace the dependence on
expertise scattered across individuals.
When you look at the evolution of IT in the enterprise, innovation has really
taken hold within the last few years. In the systems and infrastructure part
of the stack, virtual machines and the public cloud have greatly reduced the
need for server floorspace, cooling and other investments that are
overhead-intensive. That's very tangible evidence of innovation. On the
application layer of the stack, developer teams have been boosted by DevOps
tools and Agile methodologies. The evidence of that innovation manifests
itself in dev teams' ability to go faster than ever and constantly... (more)
All too often, database development is an afterthought in Agile Development.
Developers perfect how best to implement a solution in code, but tend to
spend too little time on representing that solution in the Database. This
is unfortunate, given that 65% of your change requests require changes to the
application schema, according to independent research conducted by Simon
Management Group. This finding implies that Database changes are every bit
as important as the Application Code, and should be treated as tier-one
artifacts in your release process.
At Datical, we typically ... (more)
In my first post in this series, I discussed the underpinning principles of
all DevOps patterns as eloquently stated by Gene Kim, author of "The Phoenix
Project." In this post I'd like to dig a little deeper into The First
Way. As a refresher:
The First Way: Systems Thinking - This Way stresses the performance of the
entire system of value delivery. Instead of becoming laser focused on the
part of the process for which an individual or team is responsible, the
individual or team works to understand the entire process from requirements
generation to customer delivery. The goa... (more)