Hate to be the bearer of bad news but all SDK’s are depreciated with no migration. See here
That includes functions, wire protocols, data access permissions and storing/access Atlas data.
Essentially anything related to Realm / Atlas is dead.
You’ll have to re-tool your app for another platform.
At there moment there are dozens/hundreds of us developers searching for alternate solutions but from what I gather none are “ideal” although several companies are stepping up to provide some possible solutions.
We are Swift, macOS based for our apps, and we’re not having much luck with any kind of “smooth” transition. It’s going to be a total re-write for us.
In fact, from what I researched, I already imagined this, but I didn’t want to believe it.
How MongoAtlas would simply orphan so many developers who used its technology?
The ease of using SDKs was the reason I chose MongoAtlas as the standard technology. Honestly, I don’t see any reason to continue using the same thing anymore.
Will you continue using MongoAtlas or will you move on to another database storage solution for your app?
I am confident that developers are rapidly moving all of their projects away from MongoDB as well as getting off of the Realm platform due to its demise.
There’s about 9 months remaining at this time so finding another solution is highly recommended.
We are struggling to find a Swift solution:
CouchBase has been very receptive to hosting our products but it’s way different than Realm and as mentioned, will require a complete re-write but it does offer offline and cloud storage.
We’ve worked with Parse, which we like, but the community involvement is minimal and no real offline storage. And well, the platform is a bit fragmented with 3 different versions. It’s kind of a strange platform as well.
Back4App for cloud storage has been tremendous and very welcoming, but they rely on Parse, so back to no real offline storage without running a local server.
We’ve been using Firebase for something like 10 years, and it’s a great product that’s well supported but again, totally different implementation with it being an Online first solution (and owned by Google, a downside for us).
We’ve dipped our toe in a number of other platforms but many of them are a ‘work in progress’ as far as a Swift SDK - you may have better luck with React