DBmaestro vs. Liquibase: Database DevOps tools square off
Databases are central to many enterprise IT applications, but databases don’t fit comfortably into DevOps. DevOps, GitOps and variations thereof focus on software coding and release synchronization. But what about databases?
Database technology poses a challenge for those who create DevOps pipelines. Most enterprises use SQL and relational database management systems (RDBMS). Within this combination, a database is a curious blend of programming and infrastructure.
Databases consist primarily of data, of course. Data presents a situation quite different from executable application code for DevOps cycles. You cannot stage a test database in production — it would overwrite real user information. To get around this, you can correlate test-data extracts or parallels with the real production environment, and stage parametric and configuration information, as well as code, to attempt an accurate facsimile of the live environment. But, even with strategies to abstract, DevOps database automation presents unique challenges — not the least of which include security and compliance.
Database automation vendors address these DevOps database challenges within the enterprise. In this product faceoff, we’ll compare two leaders in this market: DBmaestro vs. Liquibase. Liquibase is a commercial vendor formerly known as Datical.
A modern SQL/RDBMS or other structured database stores and accesses information in a way that aligns with most business needs. The notion of a query and a table come from this SQL/RDBMS combination. Essentially, a structured database builds a programming language around its structure, its model of access. Databases fall outside of the typical DevOps scope, which introduces human delay from the DBA review into an increasingly automated release cycle. The goal of database DevOps is to align DevOps practices and tools to create a pipeline for the database from source control through production release, just as DevOps teams do for application features. Just as handoffs between dev, test and ops delay application delivery, so too can friction occur upon the database administrator (DBA) reviews. DBA change reviews typically accompany, and sometimes even drive, application updates. Databases fall outside the typical DevOps scope, which means the DBA’s review is a human-caused delay in an increasingly automated release cycle. Even more frightening, DevOps teams might skip reviewing the database changes entirely, because their tools don’t cover these kinds of reviews or they have no policy in place for them. An unproven database change released to production poses a major risk to governance and database integrity. To reduce the DBA’s efforts in a safe manner, organizations can replace manual reviews with policy-based controls for database changes. In many cases, they can automate the handling of database changes in a similar manner as they would for new features or configuration code. Database release automation can cut weeks off the SDLC, a critical benefit when Agile or rapid development is the goal.
Both DBmaestro and Liquibase allow policy controls as input for database changes, and flag exceptions for review by a DBA. The two vendors take different approaches to the tasks. Liquibase Enterprise was previously known as Datical DB, before the company rebranded as a commercial version of the open source Liquibase. Liquibase Enterprise, which we’re evaluating here, includes many added features and a better GUI over the open source version. Liquibase integrates database DevOps with software-code DevOps, and applies policy controls created by the DBA to maintain data governance and stability. DBmaestro also enables DBA control and integrates gradually with the DevOps flow of the code. DBmaestro’s tagline is, “Automate and govern database releases to accelerate time-to-market while preventing downtime and data loss.” While reuse of components is merely a goal in development, it’s required for databases.
