What do I do now that Facebook killed Parse
January 29, 2016 12:43 AM Subscribe
No sooner had I rewritten my iOS app to rely on the backend service Parse ("hundreds of thousands of developers trust us!" it said on the website) than did Facebook kill it. What should I do?
Specifically, now that Parse is going out of business, does anyone think it is a good idea to use the new open source version? While it was nice to learn that they were releasing the code so that anyone could run a Parse server + MongoDB, I'm unsettled by the unsympathetic tone of the migration instructions and specifically by a statement in there like, "for most apps, this change-over will be non-trivial..."
My app is a user-matching app with user logins and about five tables. I am wondering if I should just switch to Ruby on Rails or something like that. I also see that there are similar cloud services to Parse, like Firebase, or even Apple's Cloudkit, but the bad news about Parse has me wary of trusting anything like that.
(I should have known better after the time I put my faith in Yahoo! Pipes)
Specifically, now that Parse is going out of business, does anyone think it is a good idea to use the new open source version? While it was nice to learn that they were releasing the code so that anyone could run a Parse server + MongoDB, I'm unsettled by the unsympathetic tone of the migration instructions and specifically by a statement in there like, "for most apps, this change-over will be non-trivial..."
My app is a user-matching app with user logins and about five tables. I am wondering if I should just switch to Ruby on Rails or something like that. I also see that there are similar cloud services to Parse, like Firebase, or even Apple's Cloudkit, but the bad news about Parse has me wary of trusting anything like that.
(I should have known better after the time I put my faith in Yahoo! Pipes)
Honestly, as someone who moved from my own AWS db/cloud solution to a third party solution (that shut down) to Parse (that is shutting down), I'd recommend your own AWS db/cloud solution.
posted by destructive cactus at 10:21 AM on January 29, 2016
posted by destructive cactus at 10:21 AM on January 29, 2016
This is, unfortunately, a risk when you get into bed with any service - backend or otherwise.
I think you've got several options:
1) Pick another service. Parse was a darling for a while, and you'd think Facebook buying it would help it survive. If, even in that context, it couldn't survive, you may want to consider services that have even higher likelihoods of sticking around. If I were to go this route, I'd pick one of AWS' backend solutions - but Amazon could still screw you.
2) Per destructive cactus - roll your own. This may include standing up your own Parse+MongoDB implementation (though, really - ugh) - but if I were to go this route, I'd pick something else.
posted by NoRelationToLea at 11:48 AM on January 29, 2016
I think you've got several options:
1) Pick another service. Parse was a darling for a while, and you'd think Facebook buying it would help it survive. If, even in that context, it couldn't survive, you may want to consider services that have even higher likelihoods of sticking around. If I were to go this route, I'd pick one of AWS' backend solutions - but Amazon could still screw you.
2) Per destructive cactus - roll your own. This may include standing up your own Parse+MongoDB implementation (though, really - ugh) - but if I were to go this route, I'd pick something else.
posted by NoRelationToLea at 11:48 AM on January 29, 2016
This thread is closed to new comments.
posted by Nelson at 7:28 AM on January 29, 2016