Parse is shutting down, shall I migrate to other BaaS or Parse Open-source offering?

 

Parse shuts down image

Image owned by Techcrunch – http://techcrunch.com/2016/01/28/facebook-shutters-its-parse-developer-platform/

As Facebook announced it will be shutting down Parse by Jan28, 2017, thousands of developers would be thinking what to do with their Parse app. There are basically three approaches to handle the situation:

1. Migrate to another BaaS (such as Firebase, Kinvey, etc)
2. Migrate to the open source Parse server and self-hosted it on AWS/Google App Engine/Heroku
3. Migrate to a managed open source Parse Server services such as parse-hosting.com

So which one better suits me?

 

Two key questions to consider:

  1. If I migrate to another BaaS like Parse, would it shut down just like Parse did? In addition, how much resources and time would I need to put into rewriting all existing parse code for the new BaaS?
  2. If I migrate to the open-source Parse Server, how much resources and time would I need to reimplement missing features like Push notification and welcome emails? Also, how much resources would I need for server deployment and management?

Pros and Cons with a new BaaS (e.g. Firebase, Backendless, Kinvey):

Pros:

  1. Enjoy another hassle-free backend.

Con:

  1. Takes weeks to months to re-design, code and test when transiting to a new BaaS with their SDKs
  2. Might risk encounter a missing features from Parse (e.g. Firebase does not have push notification)
  3. Risk of another shutdown like the sudden shutdown of Parse

Pros and Cons with open source Parse Server Self-Hosting (e.g. AWS, Heroku, GAE):

Pros:

  1. Stay independent from BaaS and run reliable service in the long term
  2. Keep using Parse client side code and no rewrite.

Con:

  1. All backend migration, upgrade, management, deployment and maintenance work has to be carried out in-house
  2. Need to reimplement missing features from Parse open source server

Pros and Cons with Parse Server hosting service (e.g. Parse-hosting.com):

Pros:

  1. Stay independent from BaaS and run reliable service in the long term.
  2. Keep using Parse client side code and no rewrite.
  3. They handle the migration for you, and reimplement missing Parse features, like push notification, webhook, welcome email.
  4. Provide hassle-free backend with easy deployment and maintenance with technical support.
  5. In case if hosted server shutdowns, you can simply take the dedicated server back and switch to other software house or in-house backend developer.

 

If you find this post interesting, subscribe to our newsletter to get notified about our future posts!

 

1 Comment

  1. Great analysis. I am a Parse user and I have just migrated it to Heroku. I must say this is a difficult decision as one has to take into account sustainability.

Leave a Reply

Your email address will not be published.

*

© 2017 Oursky Blog

Theme by Anders NorenUp ↑