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

Parse is shutting down today

status.parse.com

Post reply on HN
Print view View original

261–270 of 297 posts

Re: Parse is shutting down today

#261

Post by primitivesuave »

pier25 wrote: post #243
hackerboos wrote: post #95

Earlier quoted context omitted.

Firebase has a few issues. Take a look at this video and tell me this query and the required data denormalization is acceptable. https://t.co/xd1KUPc8xY

Yep data modelling and querying capabilities is a real deal breaker in Firebase. Something as simple as filtering by 2 or more values becomes ridiculously tedious. http://stackoverflow.com/questions/26700924/query-based-on-m...

I completely agree that on its own, the querying functionality can be quite tedious for anything complex. I linked to this solution on the comment above as well: https://github.com/davideast/Querybase

Re: Parse is shutting down today

#262

Post by pkaeding »

cperciva wrote: post #245
flukus wrote: post #240

Earlier quoted context omitted.

> Parse was an API as a service. The idea being that you don't need your own servers and parse would provide API, database, push messaging and so on. I'm still unclear. It's some sort of hosted database+services?

I'm also confused. "API as a service" sounds to me like "service as a service"... ok, it's a service, but what does it do ?

And if I download the open source code, and run it on my own server, is it a service as a service as whatever-the-opposite-of-a-service is? I'm confused...

Re: Parse is shutting down today

#263

Post by greenleafjacob »

DivineTraube wrote: post #230

A little Parse trivia a gathered from talking to (very capable) Parse engineers that now work at FB: - Still the world's largest MongoDB user - Had 1M apps, largest one with 40M users - Server was Rails at first (24 threads max. concurrency), later rewritten in Go - >40 MongoDB Replica Sets with 3 nodes each. Storage Engine: RockDB (MongoRocks). No sharding (DB-to-replica-set-mapping). Only instance storage SSDs, no…

Even with higher levels of "consistency" Mongo is still unsafe [1].

[1]: https://aphyr.com/posts/322-jepsen-mongodb-stale-reads

Re: Parse is shutting down today

#264

Post by franciscop »

bjacobel wrote: post #256
franciscop wrote: post #254

Earlier quoted context omitted.

That cannot work at all! See inside /bin/parse-server: require("../lib/cli/parse-server"); The same with the package.json, it points to /lib/index.js . However there is no /lib folder, apparently its name is /src . So there is basically no possible way that is even able to run. How is this possible? Either someone linked /src to /lib (doesn't make sense) or they changed the name of the folder and didn't change anythi…

Files in src/ are run through Babel and output to lib/ as a prepublish step. The version that you download from NPM contains a lib/ directory. https://github.com/ParsePlatform/parse-server/blob/master/pa...

That makes sense, I would have put them in /dist though

Re: Parse is shutting down today

#265

Post by hota_mazi »

nodamage wrote: post #246
hota_mazi wrote: post #241

Earlier quoted context omitted.

> which Parse only was after it had already failed You just listed some pretty impressive metrics, Parse was acquired for $85M and yet, you still think that Parse failed? I'm curious what you would call a success.

A product that is acquired and subsequently shut down because the acquirer has no interest in it is indeed a failed product as far as I'm concerned, even if said acquisition was a financial success for the investors and employees.

It was acquired because it was successful.

The failure is 100% on Facebook's side. They could have decided to keep the business up, they decided no to.

Thankfully, Google is doubling down on a similar business, so we have alternatives.

Re: Parse is shutting down today

#266

Post by mypalmike »

taneq wrote: post #257
Groxx wrote: post #217

Earlier quoted context omitted.

Huh. Yeah, I dove around a bit, browsed the wiki, etc, and so far all I've seen is the equivalent of "an open source version of the Parse backend". No description anywhere that I can see about what it does or why you should care (unless you're already on Parse, of course). IIRC the Parse homepage used to have this, but ever since the shutdown notice (so, for the past year) the homepage has largely been useless.

So many posts on HN are like this, assuming that every obscure webservice is common knowledge. "Jabberwocky has reached version 1.1! Performance increased by 30%, users must migrate from 1.0 by the 12th. Use Jabberwocky in your business now! New users get a free trial!" OK that's nice but what tf is it and why should I care?

Yesterday I built a 100M user social network using Jabberwocky. It took me just 25 minutes, bro, and now I've retired to my own private Caribbean island.
Post reply on HN