Whether you8217;re migrating from the deprecated Parse.com (api.parse.com) or building a new application, the Parse Server community is alive and strong, and since Parse Server version 2.1.11, there is support for MongoDB 3.2 which makes MongoDB Atlas an ideal back-end for Parse Server based applications.
Existing hosted Parse / api.parse.com users can migrate their back-end using Parse’s Database Migration tool directly to MongoDB Atlas using a connection string like the following (with bold items replaced with your details):
We will learn in this blog post:
- How to deploy a MongoDB Atlas cluster
- How to deploy the Parse Server (in our case we will show how to do so using AWS Elastic Beanstalk quick start, but updated to use the newest version of Parse Server)
- How to configure Parse Server to connect to MongoDB Atlas
- How to confirm connectivity
How to Set Up A New Sample Parse Server Application with A MongoDB Atlas Back End
- Deploy MongoDB Atlas cluster
- Consider sizing options but start small for a hello world style application. You can always scale later (MongoDB Atlas allows you to migrate to larger instances with no downtime to your database).
- Register for MongoDB Atlas at mongodb.com/atlas
- Build and deploy your first cluster (we’ll use a small M10 instance-sized replica set for our example, and deploy it into the US East region)
- We’ll Create a user with at least readWrite on the applicationDbName database (or the user with readWriteAnyDatabase@admin which gets created automatically will do)
- For testing purposes, we will open IP address to all IP addresses initially (0.0.0.0/0): Later we should leave only open to our application servers’ public IP addresses.
- Choose where and how you want to deploy the Parse Server:
- Many options are described here, some of which provide easier set-ups than others. AWS Elastic Beanstalk and Heroku are easy options.
Continue reading %Building a New Parse Server & MongoDB Atlas-Based Application%
thanks you RSS link