Details
-
Task
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
-
0.5
Description
Question
Can MongoDB Atlas be used as a MongoDB back-end for Parse?
Answer
There are two primary contexts in which Parse is run: the (now deprecated) hosted Parse platform, and the "Parse Server" self-managed option.
MongoDB Atlas is not an ideal back-end for pre-existing mobile apps that are pointing to the Facebook-hosted (deprecated) Parse system through api.parse.com for a few reasons
1. MongoDB 3.2 is not officially supported as a migration endpoint (though it’s no longer blocked)
2. MongoDB Atlas does not offer the failIndexKeyTooLong capability, and
3. The hosted Parse migration service does not support migration to a MongoDB cluster that authenticates against the 'admin' database.
However, MongoDB Atlas is a good back-end for Parse Server deployments (mobile applications that do not go through api.parse.com).
This means that for net new applications, or applications where a Parse developer pushes out a new mobile app version that points to a Parse stack and back-end cluster distinct from their hosted version (aka distinct from their customers on the old mobile app version), then MongoDB Atlas will be OK because in that paradigm a user is expected to manage their own indexes, and the Parse standalone server has been tested against 3.2 by the community.