I guess I'm old fashioned, but I never really "got" Parse and other hosted backend services. It's easy enough to build a backend that talks to a mongo-like database (for the vast majority of use cases), especially with help from the hundreds of awesome and free libraries/drivers out there. Plus, you don't have the risk of some business executive randomly deciding to kill your backend, and when you're debugging, it's one less chance of the bug being in the platform you're relying on and not your code (which is something you can immediately do something about).
I guess many will jump ahead and offer easy migration such as Azure:
<a href="https://azure.microsoft.com/en-us/blog/azure-welcomes-parse-developers/" rel="nofollow">https://azure.microsoft.com/en-us/blog/azure-welcomes-parse-...</a><p>(disclaimer: I work for Microsoft)
Previous code-base should rely on your own parse-server hosting IMHO. The dream of not worrying about servers AT ALL isn't exactly tangible, I think.<p>I've written a short introduction to a BaaS I've been working on in the last couple of years, it would be great if we as a community embrace new ideas and have another good tool to do a great job as Parse had been doing: <a href="https://medium.com/@endel/hook-open-source-alternative-to-parse-com-written-in-php-ad25d26c625" rel="nofollow">https://medium.com/@endel/hook-open-source-alternative-to-pa...</a>
Some quick feedback. You guys need to offer a "Hobbyist" plan for around $30-60/per month. Otherwise you are really only shooting for a very small portion of Parse users with your base price starting at $199/per month. Then again that just leaves the market open for someone else to offer more affordable prices. Good luck.
I am not using parse's backend services. I am using its push services. Has anyone had experience with Amazon Simple Notification Service? I am thinking switch to aws sns (<a href="https://aws.amazon.com/sns/" rel="nofollow">https://aws.amazon.com/sns/</a>).
Take the time to move it to a self-hosted setup. You're already dealing with a company shutting down their own service.<p>Best thing you can do is be self-sufficient and self-reliant.
Yes. AWS lambda.<p>It's micro services.
Remember 2000 data centers? Everyone was afraid to go Cloud.<p>I predict cloud is going to die, like it or not, up next is microservices by many names. <a href="http://www.programmableweb.com/apis/directory" rel="nofollow">http://www.programmableweb.com/apis/directory</a><p>That is the future.
Most of developers will worry about <i>any</i> other BaaS will shit down as Parse does. A new alternative might be in a way of "take-away-parse" hosting solution. Not necessarily open-source but would be nice if it is.
It's probably worth pointing out that if you have existing released apps that depend on Parse and you want to preserve data continuity, it's pretty much necessary to transition to Parse Server.