Flyway vs Pg_timetable: What are the differences?
What is Flyway? Version control for your database. It lets you regain control of your database migrations with pleasure and plain sql. Solves only one problem and solves it well. It migrates your database, so you don't have to worry about it anymore.
What is Pg_timetable? PostgreSQL Job Scheduling. It is an advanced job scheduler for PostgreSQL, offering many advantages over traditional schedulers such as cron and others. It is completely database driven and provides a couple of advanced concepts.
Flyway and Pg_timetable belong to "Database Tools" category of the tech stack.
Some of the features offered by Flyway are:
- Supported databases: Oracle, SQL Server, SQL Azure, DB2, DB2 z/OS, MySQL, MariaDB, Google Cloud SQL, PostgreSQL, Redshift, Vertica, H2, Hsql, Derby, SQLite
- Supported build tools: Maven, Gradle, Ant and SBT
- Works on: Windows, Mac OSX, Linux, Java and Android
On the other hand, Pg_timetable provides the following key features:
- Tasks can be arranged in chains
- A chain can consist of SQL and executables
- Parameters can be passed to chains
Flyway is an open source tool with 4.86K GitHub stars and 998 GitHub forks. Here's a link to Flyway's open source repository on GitHub.
What is Flyway?
What is Pg_timetable?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Pg_timetable?
What are the cons of using Pg_timetable?
What companies use Pg_timetable?
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.
it works with complex SQL script and it is very high customizable.