Liquibase vs LiteCLI: What are the differences?
Developers describe Liquibase as "Source control for your database". Developers store database changes in text-based files on their local development machines and apply them to their local databases. Changelog files can be be arbitrarily nested for better management. On the other hand, LiteCLI is detailed as "CLI for SQLite Databases with auto-completion and syntax highlighting". A command-line client for SQLite databases that has auto-completion and syntax highlighting.
Liquibase and LiteCLI belong to "Database Tools" category of the tech stack.
Liquibase and LiteCLI are both open source tools. It seems that Liquibase with 1.79K GitHub stars and 1.09K forks on GitHub has more adoption than LiteCLI with 951 GitHub stars and 22 GitHub forks.
What is Liquibase?
What is LiteCLI?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose LiteCLI?
What are the cons of using LiteCLI?
What companies use LiteCLI?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Flyway vs Liquibase #Migration #Backwards-compatible
We were looking for a tool to help us integrating the migration scripts as part of our Deployment. At first sight both tools look very alike, are well integrated with Spring, have a fairly frequent development activity and short release cycles.
Liquibase puts a lot of emphasis on independence with the DB, allowing you to create the scripts on formats like JSON and YML, abstracting away from SQL, which it's also supported. Since we only work with one DB type across services we wouldn't take much advantage of this feature.
Flyway on the other hand has the advantage on being actively working on the integration with PostgreSQL 11, for it's upcoming version 6. Provides a more extensive set of properties that allow us to define what's allowed on what's not on each different environment.
Instead of looking for a tool that will allow us to rollback our DB changes automatically, we decided to implement backwards-compatible DB changes, for example adding a new column instead of renaming an existing one, postponing the deletion of the deprecated column until the release has been successfully installed.