Rahul Dhodapkar

2 results

Parse Shutdown: How to Seamlessly Continue Operations with Azure and MongoDB Cloud Manager

It has now been a few months since Parse announced their shutdown, and we at MongoDB are working to develop resources and options for users interested in migrating to other environments. We previously announced our guide to migrating from Parse to AWS and MongoDB Cloud Manager and are now adding a comprehensive guide to migrating a Parse backend to Azure with Cloud Manager . Along with Parse’s moving on announcement , they released Parse Server, an open source replacement for their hosted backend. Along with Parse Server, they have provided a practical migration path from their hosted solution to a private one. To use this solution, a team needs to provision a private MongoDB database, migrate their Parse data to that MongoDB, deploy the Parse Server into a hosting environment of their choosing, and update their client to issue API calls to their new Parse Server. MongoDB Cloud Manager’s tight integration with Azure makes it easy to setup a MongoDB deployment. This guide is for mobile developers and does not assume any prior experience with MongoDB, Node.js, or Azure. Each section provides a complete, high-level checklist with detailed, step-by-step directions. In addition, there are great jumping-off points to the specific MongoDB documentation relevant to those migrating from Parse, such as how to manage indexes and set up monitoring. Migrate from Parse to MongoDB and Azure

March 31, 2016

Parse shutdown: How to seamlessly continue operations with AWS and MongoDB Cloud Manager

Editor's note: Existing hosted Parse users can migrate their back-end using Parse's Database Migration tool directly to MongoDB Atlas. See how in this tutorial . Parse was a bold offering in the burgeoning space of Backend-as-a-Service, and we’re sorry to see them wind down. MongoDB was founded to make it easy for application developers to build great products for their users, so we are 100% behind projects that serve that mission on another level; and we are proud that Parse built their backend service on top of MongoDB. Fortunately, Parse has provided their users with a viable and straightforward migration path. Along with their announcement, they released Parse Server, an open source replacement for their hosted backend. To use this solution, a team needs to provision a private MongoDB database, migrate their Parse data to their MongoDB instance, deploy the Parse Server into a hosting environment of their choosing, and update their client to issue API calls to their new Parse Server. MongoDB Cloud Manager’s tight integration with AWS and Azure makes it easy to set up a MongoDB deployment, and AWS’s Elastic Beanstalk makes deploying Parse Server relatively easy. Together with the data migration tool that Parse is providing, the transition can be as seamless and painless as possible. To that end, we have put together a comprehensive guide to migrating a Parse backend to AWS with Cloud Manager and Elastic Beanstalk. A guide to doing the same with Azure is in development and will be posted soon. Using either solution will maximize the portability and stability of your new infrastructure. The guides are aimed at mobile developers without assuming any prior experience with MongoDB, Node.js, or AWS. They provide watertight, high-level checklists, with guidance for what effort you can expect to expend at each stage, as well as detailed, step-by-step directions for each. In addition, they are great jumping-off points to the specific MongoDB documentation relevant to those migrating from Parse, such as how to manage indexes and set up monitoring. Migrate from Parse to MongoDB and AWS Learn more. Join us for a live presentation on the steps required to migrate from the Parse platform to your own deployment of MongoDB on Amazon Web Services.

February 3, 2016