MigrateDB | Tools to migrate data between realtional DB write in PHP | Database library

Premise 1: The structure of your documents will change over time due to new features, updates, etc.
Premise 2: Not all user documents will end up on your server, because sync is a premium feature.
Premise 3: The web or mobile client expects the data to come from the database in a certain structure to function properly.

--> I need to handle data migration on the client.
--> I need to keep track of all database versions / document structures that ever existed and make sure that I migrate them safely to the current version, because otherwise the data corrupts and the app cannot be used anymore.
--> If something goes wrong, there is no easy way to solve it, because the data is on the client and I can't solve it from the server.

Solution 1: I store the version of the database in a document and create a 'migrateDB' function that checks the database version during startup and migrates all documents if needed.
--> Requires less verbose code during subsequent database reads, because the client can expect the data to be safely migrated and in the right structure
--> If something goes wrong during the migration, the app basically can't be used anymore

Solution 2: The client migrates the documents on demand by checking the structure on every read and updating them if the structure is not as expected.
--> This would require very verbose code for reading documents from the database. It would have to handle every possible structure the data could still be stored in the database.
--> You will end up with a database in which some documents still have the old structure (because they haven't been read yet), while others have already been migrated

Solution 3: Solution 1 + Solution 2

Solution 4: ?

How do you deal with this?

I have the problem that migrateDb using Flyway in a Gradle project sometimes causes

I'm trying to learn the Persistent Library.

I have two files one with all the types I've defined for my project (diet tracker)

I'm using serverless to deploy an application where I use a Custom Resource to migrate a RDS database.

Everything works while I deploy, but when I delete the stack the Custom Resource timeouts after an hour with the message "Custom Resource failed to stabilize in expected time.". The request to the pre-signed AWS S3 URL returns 403 with the error code AccessDenied.

My first sent, successfull, response body to the pre-signed URL (upon Create):

I get a babel-node error. Please help me in fixing this issue.

Please see the error below