Help build your own Parse Server Hosting Environment onAmazon (AWS) | Google Cloud Platform | Heroku.

Migrate Parse Apps

Migrated 20+ Parse Apps

Parse Server Cloud Hosting

Migrated20+Parse Apps

How To SelectParse Migrate Services?

Are you looking for parse hosting and parse migration services for your current app? We provide Parse Migration services of apps to AWS, Heroku and Google cloud platform. Switch from Parse.com to self hosted platform with our Parse Migration Services!

Parse Case Study

Clients


case_stusy_A

case_stusy_B

feasty_image

ToGo_image

iron_trainers_image

Parse Testimonials

iron_trainers_image

“Great work, you guys really know your way around this stuff.”
– Jorge Ferro (CEO, Iron Trainers)

case_stusy_B

“Thanks a lot for successfully delivering the project, especially thanks to Hemant for all the hard work he has put in. We really appreciate it.”
– Sanjeev Kumar (CEO, Pingin.Social)

How To SelectParse Migrate Services?

Are you looking for parse hosting and parse migration services for your current app? We provide Parse Migration services of apps to AWS, Heroku and Google cloud platform. Switch from Parse.com to self hosted platform with our Parse Migration Services!

Do You Want To Migrate Your Apps From Parse?

Parse has been the go-to platform for many developers for developing the app backend. It gave an opportunity for the startups to use the Parse backend for free of cost until they reached a critical user base. This allowed them to flourish without worrying about the infrastructure and the cost of mobile app backend.

Facebook recently announced that they are shutting down the Parse service in 1 year. Good thing is that Facebook has also made the technology open source so that we can migrate the service to new (private) infrastructure.

Experience an easy transition of your app to Amazon (AWS) with Mobisoft Parse Migration Service.

Official Parse Migration Guide

Parse has already given a guide for migration. However the guide is quite
inadequate when it comes to making the backend production ready.

Summary of parse migration guide

Create your own parse server

Install Node.js on a server

Install the parse server module on node.

configure and start your parse server

Create your own MongoDB server

A server of size 40 GB recommended

You need to manage indexes

You need to size-up the instance based on storage requirement

Thumb rule is to allocate 10X space of the current db size

Transfer the data from parse DB to your MongoDB instance

Change the database in the parse app to your MongoDB instance

Connect your hosted parse server to your mongo instance. This will create a dev environment for your app. If this works fine, you can replicate your parse server setup for production

Real fact & downside

The Parse open source server does not contain push notifications, yet.

While managing the servers, you will also have to look out the configurations.

Parse has suggested MongoLab for MongoDB server management. However, if you use MongoLab servers for database, you will end up paying for huge data transfer costs between MongoDB and parse server.

You shall create auto scaling groups to increase/decrease your web servers according to load. You will need a load balancer to handle this transition.

If you decide to go for your own MongoDB installation

You need to create a cluster to manage high availability.

Default MongoDB installation does not ask for password. It may result into unsecure configuration and openly accessible database.

Need to manage database failover configuration, backups/restore and software/instance upgrades

If thousands of users are dependent on your service, you might want to implement a disaster recovery strategy.

You would like to look at the cost optimizations which can be performed in a hosted environment (VPC, IP management, security groups, networks, keeping instances in same or different zone and regions etc.)

Get real support from real developers

You can’t find the best outcome to a problem unless you explore all possible options.

Your Parse App to AWS Migration Process

Parse Migration Process

Recommended Steps to Build Your Own Parse Alternative

Mobisoft has the expertise of handling millions of users in hosted environment with MongoDB clusters as backend. Mobisoft is your ideal consulting partner for building a perfect environment in cloud for your app. We have been there and done that umpteen times. We have built and deployed the custom backends of more than 200 apps. We take those insights to recommend following things to you when you move to Amazon EC2 for hosting your parse backend.

Use larger RAMs and larger volumes for your MongoDB servers. MongoDB eats up the volumes like a horse.

Instead of using a single large volume, create multiple volumes and create a RAID configuration for better output.

One should be using high IO instances for the DBs.

Setup your backups from the standby instance. You can enable volume backups of 5 minute interval.

The instances should be using private IPs for communications to save on data transfer cost. Access to database port should be blocked for the IPs outside of the VPC.

Create a load balancer and attach your SSL certificate and public IP to it.

Create another VPC to manage auto-scaling cluster of parse servers

Create a parse server with medium level EC2 instance. It should match your minimum load requirement. Create an AMI from this instance.

Use the AMI to launch the instances in auto scaling group.

Integrate push notifications with Amazon SNS

Migrating to Google cloud works exactly the same where we use Google alternatives for the services mentioned from Amazon. Google has built a comparable stack of infrastructure services and we can take advantage of it.

Heroku has different modus operandi than these two. It offers managed infrastructure service. We deploy the code on Heroku with MongoDB services from MongoLab. It frees the clients from infrastructure admin/scalability/availability concerns for a slightly additional cost.

Looking for Parse Hosting?

Our experienced parse experts can assist you with smooth parse migration.
You can’t find the best outcome to a problem unless you explore all possible options.

FAQs

01. What is the recommended schedule to migrate your app from Parse.com?

The Parse.com hosting service will be discontinued from January 28,2017. If you are aiming at migrating your app or looking for Parse.com alternatives, you need to start working as soon as possible!

For most apps, the migration process is simple, and will require dedicated development time as well as skilled developer.

We recommend the following schedule for Parse cloud code and Parse hosting:

April 28, 2016: Data migrated to a self-hosted MongoDB

July 28, 2016: Finish setting up your self-hosted Parse Server and release a new app pointing to it By following the above schedule, it can give you time to develop your own Parse Server, and you can also train your development team to maintain and scale the services.

02 What are the alternatives for Parse.com?

There are some companies which provide mobile backend as a service. However we recommend you to build your own platform to avoid any issues.

03. Shall we move to AWS, Azure or Google Cloud? What difference does it make?

Any cloud service provider should be fine when you are migrating your Parse database from Parse.com cloud code. However, Amazon provides ample amount of ready-to-use services which reduces the cost of development. Keeping all things in Amazon also reduces the cost.

04. What kind of servers should one provide? and Where? How many?

For web servers, one should be using medium capacity servers. These servers should be in auto scaling groups to take benefit of hourly pricing. For databases, we should be using servers with high computing and low storage latency.

05. How can I make sure that there is no downtime during and after migration?

Perform the migration in stages.

For example, first, change the notification service from Parse to SNS. Test it and deploy it. In case of database transition, keep the production MongoDB cluster ready before transitioning. Use DB migration tool for transferring data from Parse to your MongoDB cluster. After the DB migration is complete you need to change the DB URIs in your application.

There is unavoidable few minutes of downtime when you complete the DB transition, verify it and change the configured URIs. We can minimise it’s impact by performing the transition during off peak hours.

06. How do I reduce my server costs?

Use auto-scaling feature of Amazon to increase or decrease the number of servers servicing the APIs. Prefer horizontal scaling instead of vertical scaling wherever possible. Keep the DB and web servers in the same region to reduce the data transfer costs.

07. How can I make sure my systems are secure?

Block external accesses to your database servers. Block the ports other than port 80 and 22. Allow SSH access to only restricted IPs.

08. How frequently should I take database backup? Where should I store it? How long should I store it?

As frequently as you can. You can also take volume backups. We need to find a balance between the backup frequency and number of days for which the backup is stored. Because the storage cost = number of backups per day * number of days

09. Can anybody do this for me?

Yeah. The last question is very important! You have successfully avoided the unnecessary complexities of development until now by using services of Parse.com How do you successfully dodge this bullet? You can either use a service like backend.com or you can use our help to migrate. We will take care of all these decisions for you and deploy your application so that you can continue to steer all your efforts on your application.

10. What is the difference between Google cloud, Amazon AWS, and Heroku

Heroku is managed infrastructure and hence, it requires additional costs for management. The AWS and Google cloud are cost effective solutions but one has to manage the software stack, backups, 24x7 availability, downtime, updates, upgrades and security aspects of the hosts created in these environments. Heroku + MongoLab is an alternative to AWS/Google cloud service. Both the approaches have their pros and cons, the ultimate decision is affected by criticality of the application and monthly budget allocated for the parse alternative.

AboutMobisoft

We are a leading mobile-cloud solutions expert company and we believe in fuelling simplicity with innovation to provide comprehensive mobility solutions for startups, SME’s and large enterprises. Our team is backed with numerous years of experience, latest technology skills, industry know-how and can solve the most complex business problems across all platforms.

150+Clientele
225+Team
12+Year
400+Mobile Apps
100+Web App