Must have tool for DevOps

I have not needed to use liquibase support for liquibase already has a good documentation ecosystem. Existing liquibase documentation is useful for new developers to pick up liquibase and also the set up of liquibase is extremely simple. Much of the effort needed to maintain liquibase in our apps is writing rollback statements. Although liquibase provides auto-generated rollback statements if you use its xml syntax, but its xml syntax requires a learning curve and so we only use original SQL in our changesets. The downside of using SQL is that you have to write your own rollback statements if you want to use liquibase's rollback feature.

Liquibase is suited if you have a database and the application you write is highly dependent on that database. If your application doesn't require a database, then you don't need liquibase. You should only use liquibase to apply database changes that are associate with any application change. If you want to apply a change to database to resolve a production incident without changing the application, then you should not be using liquibase.