1. Home
  2. Database DevOps Software
  3. Liquibase Reviews
  4. User Review of Liquibase
Solid building block for each Java-based business information system
February 21, 2022

Solid building block for each Java-based business information system

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Software Version

Other

Overall Satisfaction with Liquibase

There was a need to introduce structured database management instead of having a bunch of SQL scripts. Furthermore, development lacked a quick and reliable way of creating test databases with predefined schema and data to execute several automated tests.
  • Create or migrate to a defined database schema in a controlled fashion
  • Integrates well with Spring and Maven
  • Supports both "code first" and "database first" approaches
  • In some cases, differences between RDBMS products leak through the abstraction layer
  • Running schema update on application startup increases administration complexity (DB user with augmented rights needs to be configured within the application)
  • Documentation is exhaustive, but sometimes is lacking helpful examples
  • Introducing Liquibase into an existing application at first creates overhead in terms of effort and necessary dev and ops support.
  • Once established, database migration becomes a non-issue for the release process.
Once it is established, it's a relief not to have to think about executing SQL scripts in the right order on each affected database.
So far, there hasn't been a need to get in touch with customer support (take this as a compliment).
The main reason for Liquibase and against Flyway is the independence of the RDBMS product used.

Do you think Liquibase delivers good value for the price?

Yes

Are you happy with Liquibase's feature set?

Yes

Did Liquibase live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Liquibase go as expected?

Yes

Would you buy Liquibase again?

Yes

Liquibase is probably the best one for supporting multiple databases. It works well and fasts if schema changes are not overly complex. I have used it also for test data management, but it delivers a few out-of-the-box features that support this use case.