Everything Atlas Search is sticking around so Autocomplete should still work.
Best would be to move away from MongoDB. It is pretty clear they want to kill Realm in the near future.
3 Likes
It hurt me to see a multi-million dollar company not publishing a series of guides to migrate each of the deprecated services.
They will soon announce they will extend the deadline, sounding like they care.
For the User Auth, I thought of a solution, implement this automatic migration logic Auth0 uses:
That logic sounds smart enough, will try to do that on Cognito in the next months. But I believe it will work only for email/password auth though.
2 Likes
Why you do this? It cause many trouble for developers like me. We spend much time to make app with your service. Now what we do?
Big problem is you not give clear guide how to change our app. How we supposed to fix without good instruction? This make situation more bad for us.
2 Likes
Hi Joel,
Your comment sounds different from the content of the EOL and Deprecation notice. Any clarity you can bring to the status of the on-device database would be most helpful.
1 Like
I couldnât find the answer to this anywhere so asking here. In the Atlas UI there is a new menu item âTriggersâ but it doesnât contain any of the existing functions that were in the realm apps. Do I need to manually copy, paste, and re-enable each function that I used to have within the Realm Apps. Ideally atlas would automatically migrate these to the new place without customers needing to do anything.
Triggers are still application based. But they added a link to a triggers page without any selected application - thus you need to select an application an then go back to the triggers page.
They called it âunification of the user experieceâ.
Theyâve clarified elsewhere - theyâll support it for a year and then they will stop. Itâll exist with its open source license on GitHub, but no one will maintain it for us (itâs up to you and me now) and itâs unclear who will even have permission to merge changes to it.
Hi Dear @Joel_Lord, Your suggestions for Atlas Data API are completely wrong ! Even today in Vercel integration of Mongodb, Atlas Data API is used. Mongodb native Nodejs drivers are not compatible with Edge Functions of Vercel or Cloudflare, etc. If they were, we wouldnât have used Atlas Data API at all ! Deprecating a product like Realm is different than deprecating Atlas Data API. Atlas Data API (including HTTPS custom functions) is a connecting method for Mongodb on Edge Functions. Give me 1 alternative solution and we will be fine ! There is none ! Tomorrow you may even discontinue Nodejs driver ! A database company discontinuing a connecting method completely to interface CRUD is unheard in development history ! There can be version upgrades and support for previous versions discontinued, but completely stopping an interface ! Unherad of. Please reconsider deprecating Atlas Data API and Custom HTTPS Functions OR alternatively let the Mongodb Nodejs be made compatible with Edge Functions of Vercel, Cloudflare, etc.
4 Likes
100% agree @Cyro_Malek. We spent over a year migrating from AWS to Mongodb and just going live this week. Unimaginable for Mongodb to depreacate Atlas Data API, HTTPS endpoints and functions ! Tomorrow they will stop triggers, then Atlas Search, then something else ! How do you trust Mongodb !
2 Likes
Iâm still very much confused. It seems like atlas has auto-generated a new realm application called âTriggersâ and that is the only one that can be shown on this new triggers page under the atlas project. The page says the list is "Linked to the App Service âTriggersâ " and there doesnât seem to be a way to change it. I tried going into a Realm app , but doesnât change what is shown on this new Triggers page, nor do I see a setting to change it. I have two other Realm apps that have triggers which arenât shown in the list. It seems like there should just be a dropdown that lists the Realm apps and the triggers for each. From the announcement I got concerned that possibly the realm apps will be deleted, and not seeing the triggers in the new place felt like they would also get deleted. I think Iâll just wait 3mo for this to be sorted out in the UI and contact Mongo if it still seems wrong.
There are two approaches I believe MongoDB should seriously consider for Pro support customers:
-
Continue supporting the Data API for all paying customers.
-
Open-source the Data API so that customers can deploy and manage it on-premises with minimal impact to existing integrations.
As a Pro support customer, I expect a reasonable solution to this situation. MongoDBâs corporate clients need long-term stability and continuity in the services they rely on, and this abrupt deprecation does not reflect that.
1 Like
Hi Alex, it the uncertainty of its future beyond September 2025 that Iâd like to explore. I thought it was opens source now, as the phrase was âcontinue as an open-source projectâ. If it is open-source now, will MongoDB walk away next September, or will they maintain an interest and provide developer resource?
1 Like
Weâve just launched our product in March after 5 years of development⊠have no idea how we will survive to this
1 Like
Still no more reply from them. How bad this team are.
1 Like
Fortunately, Microsoft just announced support for Data API in their MongoDB vCore offering.
You could move your MongoDB to Azure.
Allow me to cite the blog post:
Why the Data API Matters
The Data API simplifies interactions with Azure Cosmos DB for MongoDB by providing a direct HTTP-based method to access and manipulate data. This feature is crucial for developers who prefer RESTful APIs over traditional database drivers. vCore-based Azure Cosmos DB for MongoDBâs Data API can be authenticated with the same MongoDB users used to access the database through the MongoDB drivers. The same roles and permissions are applicable to both the Data API HTTPS endpoint and the MongoDB TCP endpoint.
I canât help but notice that in the latest release of Realm, 20.0.0, the Realm.Sync namespace doesnât exist any more. I thought the deprecation was scheduled for next September? Does this mean that there is no Sync available from maintained code in that time?
In the other post a MongoDB employee answered that they will still maintain the realm code with sync functionnalities. I guess that means it will be necessary to track a secondary branch.
Anyway I wouldnât trust them about this and we will try to migrate as soon as possible to avoid a service interruption for our app.
Is it no longer possible to create new apps via the Atlas UI? I am following the documentation for âcreate an App Services Appâ and I donât see any options for creating a new app via the Atlas UI.
Very much agree with everything here:
I was told in another thread to use the opensource tools to supplement the deprecation:
This was my reply, awaiting some community feedback:
I could not find a solution for my use case. A number of us are using the Data API with Cloudfalre workers. We have 40-50 endpoints set up using the Data API via cloudflare workers as our backend. Since CF runs on V8 engine the Data API was a great choice. Now the alternative mentioned in docs asks use to migrate to Azure/Google/Vercel or simply set up a entire backend in itself with node/express â these are not solutions to fit this use case.
Neurelo/Hasura/Snap Logic Enterprise plans are extremely expensive for something we had working right now (until sept 25) - Even if its opensource which i think they are not; it requires us to manage the platform they will sit on top of (And pay for that too) -
A lot has been taken from under our feet with little recourse or consideration â A stop gap would be if the Mongo team could implement a driver to work with Cloudflare workers and Vercel edge functions as these are not discussed in the migration docs.
Bottom line --If you take one connection method away, provide us with a equally compelling alternative that is native, asking your customers to go fend for themselves with third party companies isnât going to sit well.