“Focus on your apps and we’ll take care of the rest.” This is the phrase that came to mind when I and many others thought about Parse.com. However, our world was rocked when we heard the news that the site was going dark on January 28th, 2007.
In this article, we are comparing expenses required to host the complete Parse solution (Parse Server + Database) in two different configurations. The first configuration covers small apps and the second covers scaling / large apps.
Small Apps – Will detail the structure required for starting apps with less than ten requests/second and minimum server-side processing.
Large and Scaling Apps – Will detail the structure required for scaling and large apps with more than 10 API requests per second.
Given the fact that Parse will be permanently shuttered on January 28, 2017, you have two options to host your apps.
1. Setting up the self-hosted Parse Server and then releasing a new app pointing to it
2. Migrating to a cloud hosting company that can provide Parse hosting service
There are pros and cons of each of these options. Here I discuss a few of them which may help you choose the better of the two that best suits you.
There are two important announcements from Parse.
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:
