Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Facebook is closing Parse

blog.parse.com

Post reply on HN
Print view View original

271–280 of 543 posts

Re: Facebook is closing Parse

#271

Post by gfosco »

supster wrote: post #228
gfosco wrote: post #2

Separately, 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.

Would it be possible to open source the Parse Dashboard? Even if it's just the data browser? I really loved that part of Parse.

We will work on that, yes.

Re: Facebook is closing Parse

#272

Post by api »

jshen wrote: post #195
nodamage wrote: post #142

This announcement just underscores the importance of having full control over your backend. Yes, it's more work, but if you're writing apps that seriously depend on backend services, it's simply too much risk to depend on anyone else. Fortunately in this case Facebook offered generous lead time to migrate off Parse.com, but they were not obligated to do so, and other providers might not be so generous in the future.…

"This announcement just underscores the importance of having full control over your backend" I disagree. If using something like this let's you get to market much faster, much cheaper, and find market fit faster/cheaper, then it's worth it. Depending on the need it can take millions of dollars and year(s) of work to then begin working on the actual business objectives.

I'd change it to "if you depend on third party services, be sure to architect things so that you could migrate if you have to."

Re: Facebook is closing Parse

#275

Post by shinymark »

aianus wrote: post #245
bsaul wrote: post #198

A few thought : 1/ parse wasn't a core service for facebook, nor a relevant source of a revenu AND their API wasn't standard. Those points combined made it very risky for people to use it. 2/ since they open sourced their API now, and the service was a paid service, there's a very high probability that someone will very soon create a 100% compatible PAAS. 3/ firebase will be next to shutdown. Not because they suck, b…

> gaming console maker (aka Sony) will have the lion's share of the gaming market Given that you need a bleeding-edge $1000 PC to run Oculus at a smooth, nausea-free 70hz, I don't see how Sony is going to get similar performance from a 2-year-old $400 console. Maybe a couple generations down the road, but not in the next few years.

Most hardware is now targeting 90hz. Even more difficult!

Re: Facebook is closing Parse

#276

Post by mayop100 »

asadlionpk wrote: post #269
mayop100 wrote: post #248

Earlier quoted context omitted.

[Firebase founder here] We'd love to know what limitations you've run into and how we can do better! Send me a tweet: @startupandrew

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.

We hear you! And we're working on it.

Re: Facebook is closing Parse

#277

Post by st3v3r »

bsaul wrote: post #182
ergothus wrote: post #137

Earlier quoted context omitted.

Not from scratch, since they are offering the server code on github (see top comment here)

i would not be surprised to see a company reusing this code to provide a 100% compatible service in the coming month.

Just one?

Re: Facebook is closing Parse

#278

Post by bogidon »

mentos wrote: post #105
gfosco wrote: post #2

Separately, 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.

Awesome, I think a small tutorial on how to migrate an existing app from Parse to DigitalOcean would go a long way!

Check this out: https://parse.com/docs/server/guide#migrating

Re: Facebook is closing Parse

#279

Post by heraclez »

ineedtosleep wrote: post #130
chrisfosterelli wrote: post #23

While I'm sure this sucks for a lot of people, I'll be honest the shutdown seems pretty fair. One year notice, detailed migration path with accompanying migration tools, and an open source release of the product itself. I didn't use parse, but this seems like a reasonable way to do it.

Oh definitely. This is a fine example of how to do a service shutdown. Sadly, I await the comments from unprepared customers next year. If you make apps and use any sort of {P,B,S,I,}aaS, do you yourself a favor and follow/subscribe/whatever to their news/release channels.

I just received an email informing me of the shutdown

Re: Facebook is closing Parse

#280

Post by snej »

nodamage wrote: post #142

This announcement just underscores the importance of having full control over your backend. Yes, it's more work, but if you're writing apps that seriously depend on backend services, it's simply too much risk to depend on anyone else. Fortunately in this case Facebook offered generous lead time to migrate off Parse.com, but they were not obligated to do so, and other providers might not be so generous in the future.…

[Couchbase Lite architect here, so I have skin in this game]

Even better, if you're using an open protocol, you can work with _either_ a hosted back-end or one you own, and move between them pretty easily. HTTP being a good example of course.

The problem is that open protocols for general purpose data sync are pretty thin on the ground. Couchbase built our sync architecture on top of CouchDB's replication protocol, which was badly documented at the time but at least open.

Couchbase Mobile (http://couchbase.com/mobile) uses this open protocol, so you can either BYO server (our own Couchbase Sync Gateway, or CouchDB) or use a hosted one like Cloudant. And you've got full access to the code (ours is all Apache licensed.)

I can't say we're directly compatible with Parse, or trivial to migrate to (the data models and APIs are different), and I'm obviously biased, but I do think it's a good alternative to jump ship to.

Post reply on HN