January 28, 2017. The date when our beloved Parse will bid us all good bye. It came as a shock to everybody when Facebook announced that they are going to discontinue the highly used back end cloud service.
This is going to create a few ripples as many of the mobile apps on various different platforms, be it iOS, Android or Windows, are being supported by Parse.
To give you some perspective, Parse stores all the data required for most modern applications, interacting with other services on the internet, user accounts, shared content, documents and purchases.
For a decade or so before Parse, everyone had to build this stuff individually.
So now that you can measure the magnitude of the tremors it may cause, we need to ensure, we make a smooth transition. Parse didn’t leave us hanging, it extended a rope by making Parse open source and by introducing Parse Server.
It isn’t all good, there are some shortcomings as well. So we are going to figure it out for you if you’d want to migrate to Parse Server or not.
Let’s have a round of good and bad to decide.
· Parse Server is a self-hosted application, so it does require you to take over some of the work Parse was doing. For most apps, this is not a lot of work or complexity.
There are already thorough guides available online. It takes about 5 minutes to get Parse Server running. After just a few minutes, you’re ready to start saving and querying data from your mobile app.
· You can develop and test your application locally. You don’t have to deploy to the cloud after fixing a typo. The cycle time for testing is close to zero with Parse Server.
· Can be hosted anywhere, and you even have the option of running multiple instances in different regions to serve a global audience.
· Offers a manual backup option, providing JSON files of your data. These backups could be imported back, but it’s not the same as a true backup and restore feature which most databases provide. With Parse Server, in exchange for needing to bring your own database you get several benefits, including index management, performance tuning, backup and restore functionality, and all of the other features your database provides.
· You’re free to implement your own restrictions, but none are imposed upon you. Parse enforced a 1,000-object maximum on queries, a 3-second time limit on database triggers, a 15-second time limit on cloud functions, and an overall 30-second limit on all requests. These were important limitations when running hundreds of thousands of apps, but are no longer necessary when you’re only running your own.
These are some of the much needed improvements in Parse Server, but that doesn’t mean that there are no limitations. There are quite a few actually.
The Bad —
- Simple Provisioning / Deployment
- Email Sign Up
- Twitter Sign Up
- Global Config
- Push Notifications
- In-App Purchase Receipt Validation
- System Emails
- Background Jobs
But don’t be disheartened, most of these can be rectified by just a few tweaks here and there.
So the benefits easily outweigh the limitations here. You might not observe the immediate impact but give it some time, it’s in it for the long game.
Parse’s tag line said-
Building apps isn’t easy, but we get you pretty close.
And now with Parse Server in the game, it got us even more closer.
To stay updated about all of our upcoming events sign up to our newsletter.
Upcoming Workshops at @ HelloMeets —
Google Analytics Workshop — 16th July | 3pm to 7pm
How should Developers & Designers work together to Speed up the work? — 17th July | 10 am to 4 am
Content Writing Workshop — 17th July | 3pm to 7pm
Blog Credits : Ishmin Singh