Also RedGate, but Flyway has some reasons to recommend it over RedGate Deploy depending on your DBAs/workflows: https://flywaydb.org/ (Though I don't think it is "complete" or "perfect", either.) EF Migrations are in a really good place now if you like/don't mind C# as a language (and you can easily embed SQL inside the C#, too, but there are benefits to being able to also run high level C# code). With today's... - Source: Hacker News / 5 days ago
When software starts using a database, it's advisable to have version control, just as we have Github to control our source code. This is all to be sure about what was executed for that specific version. For Java and Spring boot, we have the Flyway framework that aims to resolve this situation, free of charge. - Source: dev.to / 4 months ago
If you're looking for tools, like https://www.liquibase.com/ or https://flywaydb.org/, which are database-state-based schema migration toolkits - it might be relatively straightforward to build similar ones using Databricks SQL drivers. Source: 10 months ago
This is a 4th option, which should play nice with ArgoCD. The following example runs flyway as a k8s job. The desired migration changes are recorded as files within the chart. This helm chart can be integrated with your application (Using hooks to determine when the migration job is run) or run manually. Source: 11 months ago
By using an opinionated framework within the app/service (like Flyway, Migrate, Diesel, etc). Schema migrations happen on app/service start-up. Source: 11 months ago
Depending on the language or platform there are libraries you can use to manage this, such as Prisma on node and Flyway for Java/JVM. Source: 11 months ago
It's probably overkill but I've used github plus flyway at a couple places in the past which is pretty nice tool for tracking changes to a variety of db's, it's also very helpful if you ever need to replicate a db in a new region/environment. Source: 11 months ago
The grown-up way of creating a database schema is migrations, and no-one ever got fired for choosing Flyway (https://flywaydb.org/), so that's what we'll investigate today. By the end we are able to create the same schema as Exposed was creating, and then, as a second migration, add some constraints to the items table to reflect the reality of our data. And the transition from Exposed to jOOQ is complete! Source: 12 months ago
We use https://flywaydb.org/. You can do the migration before or during service start-up. We do it during. Source: 12 months ago
We just create the greetings table if it does not exist (instead of any database migration library like flyway). - Source: dev.to / about 1 year ago
I generally use flyway for this. You generally run it right before you deploy the latest version, or as part of the service. I mostly write Spring Boot services and these support flyway without issues. Source: about 1 year ago
For syncing the schema you can use a framework like flyway. Source: about 1 year ago
Also, from the "DevOps" point of view, this totally depends on what you want to achieve. If is a project that has changes on the database (new views, new tables...) on a regular basis I would consider using https://flywaydb.org/ in the pipeline. Source: about 1 year ago
We have a scala app, and use flyway (I'm not affiliated), all in version control, stored in the database, and linked to releases. Source: about 1 year ago
Flyway is already enabled as we created the project adding the flyway feature, so we only need to add migrations under src/main/resources/db/migration to create and populate greetings table. - Source: dev.to / over 1 year ago
Highly recommend you use either Liquibase or Flyway for schema management, and Testcontainers pg to run a transitive database for your tests. Source: over 1 year ago
If however you require some of the features missing from the cutdown edge version, or a tool you use for schema versioning requires it (e.g. Flyway) then hopefully this simple how-to will get you going. - Source: dev.to / over 1 year ago
Since we don't use JPA/Hibernate anymore, we will need to be handling our DB structure ourselves. Luckily, for a simple case like ours, Spring supports DB schema initialization directly (a real-world application might use a tool like Flyway for this purpose). Let's create a schema.sql in our resources folder:. - Source: dev.to / over 1 year ago
Flyway is the great tool for managing database migrations. Years ago Martin Fowler described Evolutionary Database Design and the idea still rocks. - Source: dev.to / over 1 year ago
I'm not sure Terraform is the right tool, but there are other tools to work somewhat the same. I've heard good things about https://flywaydb.org/ but haven't used it myself. Source: over 1 year ago
I'd strongly advice against both flyway and liquibase in favor to Atlas with the respective TF provider. Source: over 1 year ago
Do you know an article comparing Flyway to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Flyway. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.