What does that mean exactly, we can’t use realm after 2025?
16 Likes
Same question. I’m in the SDK documentantion and every page says that is deprecated.
Does that means that we need to move to something like Firebase? The message is not very clear
4 Likes
Funny, I just started like 1 month ago to use Realm, and it is already dying…
also been dead, I asked a question and created a issue, no response!
4 Likes
This is a really bad news…
Many of the features that made me choose Mongo are going to be deprecated…
13 Likes
Today, we announced the deprecation of Atlas Device Sync + Realm SDKs in September 2024. For more information please see:
For a version of RealmJS without sync features, install from community on npm or see the community git branch.
Link: Device Sync Deprecation · realm/realm-js · Discussion #6884 · GitHub
It was such a good product. Why is it being deprecated? Is there an alternate to Device Sync + Realm SDK? In the email announcement that was just released, its mentioned that ‘a rich ecosystem of open source and 3rd party technologies has emerged that offer solutions to meet these needs’. It would be great if they can be specific of what these alternate solutions are so that we can at least explore those. Considerable efforts have gone into development of apps, it’s difficult to hear announcements saying the product is being deprecated. How do you we even rely and trust on the other solutions that the company is offering?
7 Likes
I mean i’m pretty sure we all here are aware of the realm version without the Sync features… but that is not the question we are doing here
2 Likes
I’m not sure what he means “install from community on npm”, like do I need to setup a server where the sync data should be available, the reason I used mongodb is that everything is one place, now i have to put the sync data another place, what about the schema data type, or the rules for sync data?
1 Like
This is a very sudden announcement, and deprecating basically 90% of their App services seems crazy. I’ve always admired MongoDB Atlas services and products, but the lack of information on this announcement got me worried. They mentioned some migration guides, but I can’t find anything for Device Sync, have anyone found something related to that?
16 Likes
Hi Jamal, Device Sync will reach end of life in 2025. We are going to be building out a number of alternative reference architectures in the docs building on what’s in https://www.mongodb.com/docs/atlas/app-services/sync/device-sync-deprecation/ Realm itself (e.g. the on-device database/SDK) will remain open source.
The messaging is still very unclear to me - other than it sounds like MongoDB is totally out of mobile/desktop app development. The remaining tool is an open source, local-only product e.g. Realm.
Can we have a bit of clarity on what that means?
Does it mean ‘go use Firebase or Couchbase if your want device sync’ or does it mean there will be some other tool we can use to interface with Atlas?
Whatever the news, it’s quite surprising to potentially abandon an entire developer base (if that’s the case)
7 Likes
I think they can scratch the ‘Loved By Developers’ line off their homepage…
15 Likes
Agreed, the wording is reading a lot like “please use another database” at the moment.
4 Likes
What about users?
" Synced realms attempt to sync changes with your backend App Services App, whereas non-synced realms do not . Synced realms can be accessed by authenticated users, while non-synced realms have no concept of users or authentication."
Does that mean migrating users auth…?
5 Likes
We’ve built several applications on the back of App Service Sync (Realm Sync) - This is a huge blow to the MongoDB community 
7 Likes
MongoDB’s decision to discontinue App Sync has significantly eroded my trust in their services. I’ve invested considerable time and resources into building my infrastructure around App Sync, and a one-year notice for such a major change feels inadequate.
This announcement leads me to conclude that MongoDB’s services may not be suitable for mission-critical or long-term business projects. In the future, I’ll likely limit my use of their offerings to hobby or experimental projects only.
13 Likes
I am speechless.
We use the Device Sync SDK and the Atlas App Sync User management as the core foundation of our mobile apps. With this deprecation we pretty much have to migrate to a completely different core service, even tough this has been our main reason to go for MongoDB in the first place.
I also do not understand the reasoning behind it in the email:
Why the change
From our founding, our mission has been to simplify the world for developers when building applications. We create features where we see opportunities to streamline the developer experience and close gaps in the broader market. Since making these features, a rich ecosystem of open source and 3rd party technologies has emerged that offer solutions to meet these needs—including offerings from MongoDB’s ecosystem of more than 1,000 partners.
Didn’t MongoDB acquire Realm and Realm Server and turned it into an Atlas App Sync in the first place? Why doing that and then just killing it?
5 Likes
I was shocked when I saw this, right as I was getting close to launching my app. I’m going to drop MongoDB / Atlas and never look back.
11 Likes
Reading this carefully - it’s not just killing Realm. It’s terminating every aspect of working with Atlas in pretty much any capacity from a mobile or desktop device level; the REST interface and App Services has been removed along with sunsetting all SDK’s.
@Webmaster_Metos I also think this includes sunsetting authentication and users of apps. If there’s no SDK, then there are no apps and then no app users. So the assumption is that since Auth is part of the SDK’s, it’s sunsetted as well.
- Atlas Device Sync and Edge Server
- Atlas Data API and HTTPS Endpoints
- Atlas Device SDKs
I too was just a couple of months away from releasing a multi-year project with over $100,000 invested in its development.
I feel it would be appropriate for MongoDB to provide some response, direction and clarity.
12 Likes
I just wanted to come here to voice how incredibly frustrating this is. Just a few months ago as I was planning the architecture of a major new feature of my app, a mongodb rep told me that device sync had a number of large customers and was not going anywhere. I was skeptical that there was no good alternative to self host device sync, but because mongodb is such a large “stable” company I spent countless hours and dollars building my sync layer on device sync.
How am I ever supposed to trust that any mongodb feature or service will be supported in the long term?
Oh and the “migration guide” you offered has no information at all on a way forward, what a joke.
11 Likes