Welcome!

The DevOps Database

Pete Pickerill

Subscribe to Pete Pickerill: eMailAlertsEmail Alerts
Get Pete Pickerill via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Pete Pickerill

In the final post in this series about bringing DevOps patterns to database change management, we’re going to discuss the Third Way.  Here’s a refresher on the Third Way from the introductory post in this series: The Third Way: Culture of Continual Experimentation & Learning – This way emphasizes the benefits that can be realized through embracing experimentation, risk-taking, and learning from failure.  By adopting this kind of attitude, experimentation and risk-taking lead to innovation and improvement while embracing failure allows the organization to produce more resilient products and sharpen skills that allow teams to recover more quickly from unexpected failure when it does occur. The Third Way is by far the most intriguing of the “The Ways” to me.  I’ve spent the lion’s share of my career in early stage start-ups where cycles of experimentation, learning, a... (more)

Mainframes, WebSphere Config and Databases, Oh My!

by Robert Reeves, Datical CTO: On August 14th at 1:00 PM EST, Eric Minick (IBM DevOps Evangelist) and I will be hosting a webinar on automating deployments beyond just copying files around your datacenter.  We’ll be discussing the intricacies of Mainframe, WebSphere Configuration, and Database Application Schema Migrations. There’s been a lot of talk about infrastructure as code and we agree!  The days of keeping environment information in a printed document and between one’s ears are over.  So, let’s do the same for our Mainframe, WebSphere, and Database automation! Pushing com... (more)

The Advantages of a Model-Based Approach

The vast majority of schema management today is handled through the generation, review, and execution of SQL scripts.  These scripts can be tiny or huge; they can encapsulate the creation and relationships of several objects or they can describe a one-time alteration to a single object.  Once executed they generally leave no history of their passing other than the presence of the pieces they create, delete or modify; you can be dependent on hundreds of small scripts or on one giant script to build out new environments or evaluate existing ones.  You’re left with a schema that is ... (more)

The DevOps Database | Part 1 By @Datical | @DevOpsSummit [#DevOps]

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 ... (more)

The DevOps Database | Part 2

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)