I’m working on adding data residency support to my app Jenkins Integration for Jira.
However there is an additional complexity in the migration process that is currently delaying the release of multiple realms.
To speed up releasing support I’m looking to do it in two stages.
First releasing additional realms for new installs.
Once that is deployed, work on the migration process to support data migrations between realms.
I didn’t see any blockers when reviewing the data-residency docs for this two stage release.
Is my understanding correct that support for multiple data realms doesn’t require the dare-migration endpoint?
Hey @markrekveld,
It’s acceptable and not uncommon for apps to adopt Realm Pinning while on their journey to supporting Realm Migrations, particularly given the additional complexity which can be presented in managing data transitions.
With that said, there are certainly some you may want to consider:
- Customer’s data will be pinned based upon their current product region or product shard at installation time. Existing customers will be pinned to the existing
baseUrl which you had in your app. For all of these customers, they will see your app as Not Eligible in the Data Residency UI if they move to a different region.
- If a customer uninstalls and reinstalls your app (particularly an existing customer who was installed against your
baseUrl, but exists in a supported region shard), they may experience their data being stored in a different region. We’ve recently announced the EAP of Realm Persistence to help alleviate this.
Thanks @SeanBourke for the insight, I overlooked the reinstall case, thanks for reminding me.
I send Daniel a message hopefully the EAP is still open.