Need advice about which tool to choose?Ask the StackShare community!
Liquibase vs Slick: What are the differences?
What is Liquibase? 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.
What is Slick? Database query and access library for Scala. It is a modern database query and access library for Scala. It allows you to work with stored data almost as if you were using Scala collections while at the same time giving you full control over when a database access happens and which data is transferred.
Liquibase and Slick can be categorized as "Database" tools.
Some of the features offered by Liquibase are:
- Supports code branching and merging
- Supports multiple developers
- Supports multiple database types
On the other hand, Slick provides the following key features:
- Seamless data access for your Scala application
- Write Scala code to query your database
- All database entities and queries are statically checked at compile-time
Liquibase and Slick are both open source tools. Slick with 2.27K GitHub stars and 542 forks on GitHub appears to be more popular than Liquibase with 1.85K GitHub stars and 1.1K GitHub forks.
orat.io, Massdrop, and SpringRole are some of the popular companies that use Slick, whereas Liquibase is used by Orbitz, Viadeo, and Virgin Pulse. Slick has a broader approval, being mentioned in 7789 company stacks & 4 developers stacks; compared to Liquibase, which is listed in 22 company stacks and 68 developer stacks.
Pros of Liquibase
- Many DBs supported18
- Great database tool18
- Easy setup12
- Database independent migration scripts8
- Database version controller5
- Unique open source tool5
- Precondition checking2
- Supports NoSQL and Graph DBs1
Pros of Slick
Sign up to add or upvote prosMake informed product decisions
Cons of Liquibase
- Documentation is disorganized5
- No vendor specifics in XML format - needs workarounds5