Migration Handling

[akshat-kumar-singhal]

Overview

gofr currently creates migration table/records in each of the datastore it's connected to for migrations being run on any of the data stores.

Issue Faced

Multiple applications are using a single Redis instance as cache (not the ideal implementation) - migrations in those applications (on SQL) are conflicting because of migration entries getting added in Redis

Suggested Implementation

Framework should maintain the migration table/recored only in the respective data store where the migration is running and not in all the connected data stores.

[aryanmehrotra]

Yes, also one more issue faced with pubsub migration is, there is possibility of messages being published to same pubsub configuration under different topics in that case multiple services migration will not be atomic, if the migration is limited to the datasources it is being used in then these issues will be mitigated.

We can point out different issues and based on pros and cons we can decide further