I was recently joined by Chris Yates, Senior Vice President, Managing Director of Data and Architecture at Republic Bank for our webinar, Gain the competitive edge with a monitoring tool. The session sparked an insightful conversation around estate monitoring from the perspective of a Senior VP, and I wanted to share some of the key take-aways.

This is the third part of my DevOps 101 series, so before we get going, let’s do a quick recap of what we’ve covered previously In DevOps 101: What, who, why, and how, I talked about how the definition from Microsoft’s Donovan Brown encapsulates DevOps succinctly as: The union of people, process, and products, to enable the continuous delivery of value to the end users.

Development teams are under increasing pressure to keep up with the demand for faster delivery of database changes, while ensuring code quality isn’t compromised. This pressure comes from both business requirements and industry expectations. The 2021 Accelerate State of Database DevOps report reveals that the number of teams who are elite performers is increasing year-on-year (making up 26% of those in the study) and these teams have more frequent code deployments and a lower change failure rate.

The desire to release features faster and deliver value to customers sooner is prompting many IT teams to adopt DevOps and Agile practices. By automating parts of the development process where possible and working in shorter cycles to release small changes more often, those teams that do well experience fewer errors and produce higher quality code. All of which is good news, until it comes to the database.