Flyway vs RailsAdmin: What are the differences?
Developers describe Flyway as "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. On the other hand, RailsAdmin is detailed as "A Rails engine that provides an easy-to-use interface for managing your data". RailsAdmin is a Rails engine that provides an easy-to-use interface for managing your data.
Flyway and RailsAdmin can be categorized 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, RailsAdmin provides the following key features:
- CRUD any data with ease
- Custom actions
- Automatic form validation
"Superb tool, easy to configure and use" is the primary reason why developers consider Flyway over the competitors, whereas "Easy setup" was stated as the key factor in picking RailsAdmin.
Flyway and RailsAdmin are both open source tools. It seems that RailsAdmin with 7.09K GitHub stars and 2.08K forks on GitHub has more adoption than Flyway with 4.2K GitHub stars and 915 GitHub forks.
According to the StackShare community, Flyway has a broader approval, being mentioned in 15 company stacks & 19 developers stacks; compared to RailsAdmin, which is listed in 6 company stacks and 4 developer stacks.
What is Flyway?
What is RailsAdmin?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
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.
So we started out with a service called Adminium, it was really useful. But when we hit the table limit, we realized we were paying for something we could easily get for free. My friend Cyrus suggested RailsAdmin, so we made the switch. I like RailsAdmin because almost everything works without any configuration. It’s basically a UI for your PG db. We use it to debug issues and update content.