Earlier quoted context omitted.
Why?
Everything breaks at "host your data".
Any hosting/cloud service provider 'hosts your data'. I'm curious if you run your webservers in-house?
Facebook is closing Parse
461–470 of 543 posts
Re: Facebook is closing Parse
#462Earlier quoted context omitted.
Switching supermarkets is much, much, easier than switching backends. I'm sure lot more BaaS companies will pop up to grab former Parse customers. I'm not sure how many of those will still be around in another 5 years. I strongly suspect there's something negative about the economics of BaaS services that's being implied by the fact that two of the most successful providers have shut down after acquisition.
Amazon has fully embraced BaaS. And I don't know of any AWS services they've added and then removed. I think Amazon will be the winner here. MSFT is also starting to embrace BaaS. Of course they have a less stellar history of support.
True but they still lack a wrapped and simple to use solution like Parse. That is why I run everything on AWS except the BAAS.
Re: Facebook is closing Parse
#463Earlier quoted context omitted.
Well I love Firebase, but to put it naively, Firebase needs more advanced queries. Even more than usual because it is running 'far' from my backend, so queries from backend are expensive. For example, if there was a way to selectively bring back children of an object etc. I know there are workarounds (and I am doing those) but since Firebase is a DBaaS it needs to account for that when compared to other DBs.
This really seems like a limitation of nosql/mongodb, would it be worthwhile to reconsider sql/nosql trade offs?
Schema design allows you to grab stuff you want joined all at the same time (aka the data lives together in a document) in mongodb's model. This obviously has limitations in many to many relationships where the access pattern isn't clear, but often these tradeoffs can work.
Re: Facebook is closing Parse
#464Dashboard is essential. Thanks in advance for releasing a fully functional open source Parse dashboard.
Re: Facebook is closing Parse
#465Dashboard is essential. Thanks in advance for providing an open source Parse dashboard today!
Re: Facebook is closing Parse
#466That's not good news for many of Parse users :(
Here are some of the options to move on,
- https://www.firebase.com/
- http://www.kinvey.com/
- http://shephertz.com/
Re: Facebook is closing Parse
#467Earlier quoted context omitted.
That's exactly our thought (hasura.io) while we prepare for our "launch" next week. We've been studying Parse's growth and are definitely going after their market. Our core philosophy with the BaaS is however to keep it as open as possible. We wrote this up in response to Parse shutting down: https://news.ycombinator.com/item?id=10994104
Is it production ready?
Yes! We have over 20 apps build on in during our alpha phase - ranging from e-commerce to payment wallets. Let us know if you'd be interested to try out the beta version releasing next week. You can write to us at build@hasura.io or @HasuraHQ.
Re: Facebook is closing Parse
#468Earlier quoted context omitted.
Alas, open sourcing Reader wouldn't have done much: the code's all tied heavily into Google internal infrastructure. (Full disclosure: my team pulled the plug on Reader.)
Interesting the Reader developers chose their own infrastructure over "best of breed" Google AppEngine?
Google Reader initial release: October 7, 2005
Google App Engine initial release: April 7, 2008
Re: Facebook is closing Parse
#469If folks need help migrating, you can get it done quickly and cheaply with some help from Toptal ( http://www.toptal.com/#select-uncanny-hackers-today ) -- this sort of stuff is right up their alley..
Don't spam please.
Re: Facebook is closing Parse
#470Separately, we developed an open-source Parse-compatible API server for Node/Express. https://github.com/ParsePlatform/parse-server This, along with the database migration tools released earlier, allow developers a full migration path to move from Parse hosted data + API to their own infrastructure. Over the weekend, I set up a website & app on a $5 DigitalOcean box running Parse and Mongo locally.
Hey everyone looking for a migration path out - we have a “DevOps-as-a-Service” model where we can migrate Parse folks to AWS (not DO unfortunately) with full infrastructure automation, immutable infrastructure, autoscaling, chatOps deployments, monitoring and alerting, etc. for a flat rate. We have a platform that we’ve built that makes this possible - think of it as a Django/Rails/etc. for AWS: https://www.reactiveops.com/devops-as-a-service/
Although we have a framework, it lives in your github and runs in your AWS - there's no lock-in whatsoever. Ping me at matt [at] reactiveops dot com if you're interested!