19 July 2018

1 Comment

19 July 2018

1 Comment

The march of DevOps from the backroom to the boardroom

By Raysonho @ Open Grid Scheduler / Grid Engine - Own work, CC0, https://commons.wikimedia.org/w/index.php?curid=52175188By encouraging collaboration and teamwork, removing the barriers between development and operations, and introducing automation, DevOps speeds up software delivery and enables features to move from the fingers of developers into the hands of customers faster.

It’s an important topic to stay current with because software development is no longer confined to the usual suspects like Google, Microsoft and Amazon. Virtually every company now relies on technology to support their business efforts, and for many it has become a core part of those efforts.

Think of getting a quote for your car insurance, ordering anything online, making a call to customer support, buying a concert ticket, or any of a myriad of other actions that are now eased and enabled by technology. In each case, introducing DevOps into the software development that drives that technology has been proven to accelerate the process, reduce errors, and give companies a competitive advantage.

There’s a new kid on the block too: the database. Behind many of the applications that businesses rely on, there’s a database keeping a record of transactions, online behavior, and changes in customer data. When the application is updated, the database often needs to be updated as well.

Companies are now recognizing that the same DevOps processes that bring big benefits to the development of applications also need to be introduced to the development of databases, or they become a bottleneck in the process.

As a result, software tools have been created by companies like Redgate which integrate with and work alongside the same infrastructure used for developing applications. So developers can work on updating the application and the database at the same time, in the environment they’re already familiar with, and ensure the speed and efficiency that DevOps brings is not held back.

There’s an additional – and timely – business benefit too. The recent introduction of data privacy regulations in Europe and California along with the many stories about data breaches have made data protection a topic that is now discussed across boardroom tables.

Fortunately, including the database in DevOps prevents mistakes reaching production, automates many processes that otherwise introduce errors, and provides an audit trail of changes for audit and compliance purposes.

So if you’re undertaking a DevOps initiative, remember to include the database as well. Your business will move faster and at the time you’ll take a significant step forward in meeting the increasing demands to protect your customers’ data.

This article was originally published in the Summer 2018 issue of Microsoft’s enterprise magazine, The Record.

If you’d like to know more about extending DevOps practices to the database, read Redgate’s whitepaper, Solving database deployments with database DevOps.

Tools in this post

Share this post.

Share on FacebookShare on Google+Share on LinkedInTweet about this on Twitter

Related posts

Also in DevOps

CALMS and how it relates to Database DevOps

CALMS is the acronym for a framework which allows businesses to assess how prepared they are on their journey to DevOps, and where they can improve. CAMS (without the L) was first introduced by Damon ...

Also in Blog

Have your say on the future of data masking

Back in 2017 Redgate acquired Net2000, a leading provider of data masking solutions for SQL Server databases. Since then, we’ve invested heavily in the data masking tools to ensure our customers can...

Also about Database DevOps

How to reset your development database in seconds using SQL Clone

Let's say you're making experimental changes to your development database and, to explore a hypothesis, you've just dropped a table. How long does it take you to restore the database to its previous s...

  • Greg Sohl

    “including the database in DevOps prevents mistakes reaching production”. That’s fantastic! No more mistakes in production!