[DOCS-8526] Add FAQ item around MongoDB Atlas and Parse Created: 08/Aug/16 Updated: 09/Feb/17 Resolved: 09/Feb/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Atlas |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Davidson | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 7 years, 6 days ago | ||||
| Story Points: | 0.5 | ||||
| Description |
|
Question Answer 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 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. |
| Comments |
| Comment by Kay Kim (Inactive) [ 09/Feb/17 ] |
|
sunsetted. |
| Comment by Kay Kim (Inactive) [ 09/Feb/17 ] |
|
As good a resolution as any Will skip for now then. Thank you! |
| Comment by Andrew Davidson [ 20/Jan/17 ] |
|
ravind.kumar you're right that this is now out of date. "3. The hosted Parse migration service does not support migration to a MongoDB cluster that authenticates against the 'admin' database." is no longer true so hosted Parse can indeed migrate directly to atlas (we're really at the tail end but it would be nice to update this folks in case people are looking for last minute migration options) |
| Comment by Ravind Kumar (Inactive) [ 14/Jan/17 ] |
|
andrew.davidson are the steps at this blogpost accurate? It seems like this QA should have two primary points:
|
| Comment by Andrew Davidson [ 26/Sep/16 ] |
|
Some reasonably good news here: FB/Parse has unblocked the &authSource=admin capability in the migration URI. I've successfully migrated in a micro test. It does not look like the other issues are blockers |