It looks like I will migrate to Convex vs. MongoDB
They have realtime by default, you dont need to subscribe to schemas and such as in realm, and they will auto generate the schema for you just like mongodb, they have actions (triggers), can also have embedded objects and arrays, and authentication.
Discord for questions > Discord
Just another furious developer. 2 weeks from shipping a new big app project on realm sync, months in the making. And now this! What it is Trump says, GFU? Crazy, since the SDKs has matured so much over recent times.
I discovered the Realm long before MongoDB acquired it. It worked like magic, was super fast, and was super easy to use. I consider it one of the greatest innovations in mobile technology ever.
We had a huge enterprise application that was using SQLite as its database. We were not happy with the performance and decided to migrate to the Realm database. It was an indescribable experience. One complex report took about one minute to generate using SQLite, and after migrating to Realm, it took 2-3 seconds. The whole application has become much more responsive.
Even though I loved the Realm offline database, I was a bit skeptical about the cloud sync feature back when the Realm was a separate company. We desperately needed a cloud sync capability for our app. After MongoDB acquired Realm and introduced the partition-based sync, it came at the right time, and it took us comparably little effort to integrate MongoDB cloud sync into the app without significant changes in how it worked - since it would just query the offline database. This migration happened several years ago and became one of the essential features of the application that gave us a competitive advantage in the market with a unique offline-first experience in low network conditions and seamless synchronization when the connection was recovered.
Last evening, the news about Atast Device Sync deprecation came as a substantial unpleasant surprise. The application cost hundreds of thousands of dollars to develop. It heavily uses the Realm database, and cloud sync is its main feature.
I think the community deserves a better explanation than “it’s the path to the future” about why this happened. And more importantly, MongoDB should give us more details to address the following:
This just feels like the end of MongoDB Realm/App services. You are deprecating key features so we already have to look at other solutions. I also just saw that the access to the App services applications now is kinda hidden with the “App Services” tab being removed. This feels really like you don’t even want people to use App Services anymore because you know it will be deprecated soon.
And btw since you provide less service, when will the prices decrease?
I just finished migrating my app to Mongodb Realm last year thinking Atlas was a solid product run by a reliable company.
I think this deprecation move means the end of my app/company.
One year is a very short time to move to a different solution when you don’t have a lot of ressources.
This is very sad.
This post seems to be explaining what’s happening with Atlas sync.
Introducing a new partner solution is fine but they could have run this parallel to Atlas sync rather than taking it off altogether. The use cases for the both the solutions seem different.
What MongoDB is doing is definitely not fair!
So I’m not the only one that is frustrated about this news! Months of development and at the edge of releasing our app, and now suudenly it’s being deprecated.
the thing is that they just released on sept 09 a blog stating to use device sync!
check it out.
Halting Development on MongoDB Swift Driver | MongoDB (I think they should communicate)
I couldn’t agree more with @Gagik_Kyurkchyan we need better answers.
Device sync was the perfect solution for our case, it was easy, works like a charm.
I’m just wondering why their CEO took this decision? years of building atlas service, and now they are killing it. Speechless to be honest.
As my predecessors have already mentioned, we also invested a significant amount of time in integrating MongoDB Device Sync. Unfortunately, we are now back to the starting point in development.
Moving forward, we will no longer consider using MongoDB products, as this poses a significant economic risk.
Moreover, I think we are entitled to a thorough explanation of the specific reasons.
Sad new, I’ve also developing a applications for months now based on Atlas App Services. Luckily I don’t use any of the affected features, except for the Realm web SDK.
How sure can we be about the future of the other App Services features?
Being, the Data Access; rules, schema, app users, authentication, …
I’m already looking into alternatives as this is making the future of App Services very unclear.
Can’t MongoDB assure us that the other features will remain support for years to come?
can any one tell what whole of this mean in easy words??
safe time & go to other service or some features only, are my app users cant reach there information any more after 12, march, 2025, what to do exactly???
Deprecating Data API and Htps Custom Functions is an huge huge issue. How do we connect to Mongodb on Edge functions like Cloudflare or Vercel ? They need to rethink on this at least. Realm and Data API are different use cases. It is damn frustrating ! Definetely a lot of companies will be stranded and Mongodb will lose a lot of trust in this for sure !
OMG, our company was using Realm Sync first back in the days then it became deprecated… Then we spent enormous resources to migrate to Atlas SDK and now it became deprecated… It’s really frustrating!!! No trust in Mongo DB!!!
This is a disgrace. We’ve invested over 2 years development and are just weeks off launch. Losing Atlas Device Sync destroys the core functionality of our app.
MongoDB should have worked with their partners to provide alternative solutions before jepodising so many large-scale implementations of their product.
What about Functions and Authenticate & Manage Users? These would be inaccessible without Device Sync, no?
Only reckless and non-founder would this, I can suspect something is wrong with MongoDB management, and no way I will trust Mongo again, thanks to break my trust 
It is quite an incredible decision and came as a bit of a punch in the gut for me. I am not a $$$$ business, just a solo developer, so it is very sad to see the time I have spent working on my app that totally relies on Device Sync (plus auth etc.) now rendered completely worthless. I am pretty sad and speechless about it to be honest. I just don’t have the time or resources to convert everything I have worked on over the last few years to AWS or something, I wouldn’t even know where to begin and the thought of moving user auth from Realm to another service…
It feels like a very cold-hearted decision from MongoDB. Also extremely disrespectful to those it has encouraged and made promises to over the years to use its service. I certainly wouldn’t touch another MongoDB product again after I know what kind of company this is now.
Pity; I have invested a lot of time into Atlas and been looking forward to using it for the next 10-20 years and most upcoming customer projects.
This once again shows that self-hosting and Open Source software is the way to go.
This is egregious. Really non-developer friendly move. I and others will find it difficult not to have ill will towards this move. People’s entire applications and backends are running on this.
At least have the decency to 1) make the sunset period longer (2 years would be more appropiate), 2) open-source the Atlas Device Sync codebase so self-hosting could become an option.
That’s why they bought it in the first place. We are royally * here, there will be a masive effort to migrate, this time to a pure cloud at one of the big three.
Nothing really to add except me too.
Never mind, thought of something:
Links to other services are not the same as migration guides
The AWS AppSync guide to MongoDB uses GraphQL (deprecated) and DataAPI (also deprecated), so… 
I can’t believe @Ian_Ward is silent on this.
There must be some craziness going on behind the scenes because all of the regulars aren’t saying anything.
@Dachary_Carey @Andrew_Meyer @Andrew_Morgan @Jason_Flax anyone?