Flyway vs pgweb: What are the differences?
Flyway: Database Migrations Made Easy. Easy to setup, simple to master. Flyway lets you regain control of your database migrations with pleasure and plain sql. Solves only one problem and solves it well. Flyway migrates your database, so you don't have to worry about it anymore; pgweb: Web-based PostgreSQL database browser written in Go. This is a web-based browser for PostgreSQL database server. Its written in Go and works on Mac OSX, Linux and Windows machines. Main idea behind using Go for the backend is to utilize language's ability for cross-compile source code for multiple platforms. This project is an attempt to create a very simple and portable application to work with PostgreSQL databases.
Flyway and pgweb can be primarily classified as "Database" tools.
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, pgweb provides the following key features:
- Connect to local or remote server
- Browse tables and table rows
- Get table details: structure, size, indices, row count
Flyway and pgweb are both open source tools. pgweb with 5.94K GitHub stars and 419 forks on GitHub appears to be more popular than Flyway with 4.2K GitHub stars and 915 GitHub forks.
What is Flyway?
What is pgweb?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose pgweb?
What are the cons of using pgweb?
What companies use pgweb?
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.