You would think they could have found someone to take it over?
Facebook is closing Parse
131–140 of 543 posts
Re: Facebook is closing Parse
#132Earlier quoted context omitted.
I think Firebase's position is a bit more defensible -- Google has done well to ingratiate Firebase as a backend for angular apps.
The news i have heard from various googlers is, `GOOG acquired Firebase because a project started using Firebase as backend and grew very fast and they didn't want to migrate and just acquired FireBase`.
This is not even remotely true.
Disclaimer: I work on Google Cloud but not Firebase.
Re: Facebook is closing Parse
#133I don't understand why Facebook never integrated Parse into its own datacenter infrastructure. As far as I can tell, Parse still hosts all of its infrastructure on EC2 (DNS lookups for every Parse service point to an EC2 IP address). Hosting on EC2 made sense when Parse was an independent company, but didn't they sell to Facebook so they could benefit from Facebook infrastructure?
This seems like Facebook throwing in the towel on what seemed like a good plan to gain a foothold in the cloud space.
Either that, or they're not really shutting down, and they just want to get a bunch of free labor from open source developers before migrating to an enterprise support business model.
Re: Facebook is closing Parse
#134Currently using Parse for Push notifications (it's simple to send a request to Parse and it handles iOS vs Android issues). Is there any tool out there that has similar functionality? Ie. you register all your users devices there and they simplify the sending of push notifications.
It's not quite as simple to use but Amazon SNS works decently and I doubt it will shut down any time soon :-)
Re: Facebook is closing Parse
#135Platforms are for the naive.
After a few turns at the merry go round the newbie developers learn this hard lesson.
Re: Facebook is closing Parse
#136Wow. The 30 minutes you saved by using parse turns into a major headache. This makes me hesitant to use react and react-native.
The thing is it was not just 30 minutes. Between the built-in push notifications, admin console, great geo support, and easy scaling it was a complete godsend for building MVPs in a reasonable amount of time. It will be missed by many, many independent developers & consultants.
Re: Facebook is closing Parse
#137Well, this sucks. My company is about to get acquired for our technology. A huge part of the tech relies on Parse. I mean they were charging for it! Who would think that they will shutting down? I guess we'll have to rebuild that part from scratch starting right now.
Not from scratch, since they are offering the server code on github (see top comment here)
Re: Facebook is closing Parse
#138Open Sourcing the platform is always the good thing. Probably both Twitter Fabric and CloudBoost.io will be the next Parse out there. CloudBoost.io is open on Docker and is both self-hosted or managed.
Re: Facebook is closing Parse
#139This is bad...Cannot imagine how many people will freak out when AWS shut down....Just kidding
Re: Facebook is closing Parse
#140Earlier quoted context omitted.
...except being able to integrate with an API does not mean you have the ability to self host, run, and maintain the product.
If you can't self-host because you don't have the ability to, but can't use cloud services either because they could shut down, what alternatives do remain?
I think use an open source platform which has both self-hosted and managed as options. So when managed shuts down, You can self host it. I'm the founder of CloudBoost.io - and We're an alternative to Parse. We're both on Docker (Self-hosted) and Managed at CloudBoost.io