To be honest this looks like half-baked. Couple of points: - migration queries for up and down should be persisted. Here migrations are always read from files.

To be honest this looks like half-baked. Couple of points: - migration queries for up and down should be persisted. Here migrations are always read from files. If one changes down migration it might not match the up migration. - migration content should be tracked (crc, hashing, whatever) to prevent any changes to migrations once applied - my opinion is that each migration should have strict order and not be relied upon file sorts to prevent adding migrations in the middle of existing ones. This is accomplished by enforcing each id/migration number in files to be incremental - 1-to-1 mapping should be enforced and errors should be produced if there are migrations in database, but not present in files - one nit pick: two tables for migrations seems overkill This is mostly coming from Java background and having the above things was really life saver in some situations. I think the Playframwork's way of managing migrations was really good. Flyway is good too for SpringBoot (not sure if exists something besides it), but lacks down migrations.