神刀安全网

I’m still developing my app on Parse.com. Should I stay or should I go?

I’m still developing my app on Parse.com. Should I stay or should I go?

There are two important announcements from Parse.

  • Post April 28th, apps which have not migrated their database would assume a lower priority of traffic.
  • Parse will ultimately shut down after January 28th.

If you are half way through developing an app, you must be deciding about the right time to migrate.You need not be panicking right now because the performance that Parse will deliver it’s enough to finish your app’s development. Additionally. The April 28th deadline has no impact on you because there are no users for your app yet.

But there are other good reasons to move now, especially to anticipate issues on Parse migration and on to adapt Parse features. You need to figure out alternatives to build, host and manage your app.

Let’s analyse some scenarios:

A- Self-hosting a Parse server

Pros:Parse server has been open sourced. So it gives you total control of the code. You could add your own features if you master the server code.

Cons:Setting up a local parse server and deploying your app is not easy. Migrating the DB to a self-hosted MongoDB as suggested by Parse and connecting it to a local instance of Parse server is quite a task. Also, currently, not all features of Parse server is open sourced. So you may still not be able to rebuild it all using local instance.

B – Look for an alternate BaaS provider

Pros:If you don’t want to host things yourself, there are other commercial alternatives to Parse, replacing part of the services it offers.

Cons:How can you guarantee that the new BaaS provider will not raise their hands someday similar to Parse? Also, they have an entirely different API and technology you’ll need to learn. So you will have to re-write your front-end and API code to make it compatible with their platform.

C – Get your backend entirely rewritten and develop your own server

Pros:The applications become totally under developer’s control without any dependency. Rebuild your current JavaScript backend from Parse into full-blown NodeJS application. If you don’t use complex features like Push, Jobs, Webhooks on Parse and just have CRUD operations on top of MongoDB database won’t it’ll be smooth. That will give you complete control over your backend and data, without locking you in on any platform.

Cons:This option demands too much effort for build an entirely new backend. If you don’t have any backend skills, I don’t recommend it. Additionally, it could work well only if you have the simple application if you have a complex application using most of the Parse features I won’t recommend it too.

D –  Look for a Parse hosting providers

Pros:If the BaaS uses Parse technology, there is no learning curve, no new technology to be implemented. You have time to migrate your app, connect front-end with the backend, test and anticipate issues when your app goes Live. This option could work out with minimum hassles.

Cons:You need to look for an additional Platform provider to host your app.

  • If you decide on a BaaS that uses Parse, additionally you need to watch out for some features like:
    Make sure it is easy to migrate from here if needed. (If the backend is open source, it would be easy to migrate anytime).
  • It provides all the features of Parse like SDK, Dashboard and also offers alternatives to the features like Cloud Code, CLA’s, Jobs, Webhooks and Analytics which is not open-sourced yet by Parse. ( Learn how to use Parse Cloud Code on back{4}app ).

If you are still developing your app on Parse, you have time till July 28th to complete your development, try one of the best-suited options stated above and test your app before it goes Live. A prompt advice would be to do it as early as possible.

转载本站任何文章请注明:转载至神刀安全网,谢谢神刀安全网 » I’m still developing my app on Parse.com. Should I stay or should I go?

分享到:更多 ()

评论 抢沙发

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址
分享按钮