We want to acknowledge that we hear the impact the end-of-life of these services has on you and your users. We understand the challenges this change brings, and we are committed to provide clarity and support during this transition.
To assist, we’ve updated our website with additional context and responses to many of your questions.
We are actively working with partners to deliver full-featured integrations, and plan to announce additional partner alternatives in the near future.
We recognize that these features are integral to many of our customers’ products and services, and some may need additional time and support to move to an alternative solution. Rest assured, we will be checking in with our customers on their migration progress and are committed to working with each of you on a path forward. In particular we understand that many of you are concerned about the Device Sync timeline. If you feel that you need more time, please reach out to your account executive, MongoDB Support Portal, or if you are not a subscription customer, please use the chat feature when logged into MongoDB Atlas.
Can you also confirm that realm-web SDK will also be deprecated? We use this to access our Atlas app db from the web browser and have built a whole lot around it.
And lastly the DATA API, which we use fairly well with Cloudflare functions.
Pls do suggest alternative for above that do not require another paid subscription.
Hey you guys can assist by making app services downloadable for self hosting. Mongo DB purchasing Realm only for you guys to kill it is just unprofessional. Allow devs to self host if you are tired if it.
If you already had a Device Sync app set up and actively running, then it will be available to you. You’re not allowed to create a new Device Sync app, though.
Correct: creation of new apps using the Device Sync feature isn’t available anymore.
Is realm web part of device sync, and is this deprecated too. The npm package realm-web which allows clients to securely connect to mongo db atlas, is this being deprecated too?
@Paolo_Manna My app is using C# SDK for Windows desktop app, and Swift for MacOS app, in your alternative page, I don’t see any migration guide for those platforms.
The Device Sync Deprecation page lists migration guides by destination platforms: while some of them support desktop environments, others don’t, and are more focused on the mobile side of things.
Please evaluate the possible alternatives, ideally together with your MongoDB representative, and directly query the best options about your requirements: many platforms are planning updates precisely to accommodate Device Sync migrations.
At least when you deprecated this Device Sync, you HAVE TO provide the alternatives for ALL PLATFORMS. After 3 months from your announcements, NOTHING ready. Are you kidding with our products? What will happens if no support for desktop environments in the next 9 months ?
Please re-read my comment: there ARE solutions for desktop environments
Please take the time to read the page and explore the proposed alternatives. Again, we won’t suggest one or another without a clear understanding of the use case, that’s why keeping in contact with your representative is a suggested step.
@Paolo_Manna I read your page MULTIPLE TIMES Ditto : only Swift, Kotlin. No C# for Windows desktop or React Native PowerSync : No C# for Windows desktop supported yet. Objectbox : Coming soon, Join the waiting list
You call them your “proposed alternatives” ???
My use case : Sync data between mobile, desktop as the current Data Sync still doing.
I don’t know who’s my representative, and you should answer the questions public, so others can know.
You’ve limited yourself to 3, down the page there’s also, for example, Parse, that’s open source, has been around for over a decade, and has SDKs that are quite extensive, including a catch-all REST API. Additionally, it has the advantage to operate on the very same database you already have, as MongoDB is fully supported.
At the cost of repeating myself, Parse may or may not be the right choice for you, but asserting that there are no alternatives just isn’t correct.
Unfortunately, I can’t help you here, as this is a public forum: if you have a Support Contract, please open a case about the matter, and we’ll be happy to follow up with you there.
I am doing that, however, once again, the right choice needs to be evaluated for each use case.