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

241–250 of 297 posts

Re: Parse is shutting down today

#241

Post by hota_mazi »

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…

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

Re: Parse is shutting down today

#242

Post by PhantomGremlin »

beachstartup wrote: post #140
djm_ wrote: post #128

Earlier quoted context omitted.

I was wondering if you have a public policy in place which outlines what would happen in the event of a Parse-like shutdown or other end-of-company-life event occurring? I ask in the hopes that it won't be taken as too negative a question but your company is VC-backed in the database space and we've lost a few too many of those this last year.

if you run a company or product, it's on you to make sure your data is recoverable and your product is fixable in the event of an outage. expecting a vendor to tell you exactly how they're going to fold is something they can surely dream up and send to you so you feel better about the nature of the universe, but something you shouldn't really rely on. in other words, assume the worst will happen, despite assurances o…

in other words, assume the worst will happen, despite assurances of the contrary.

And, just to emphasize, having a small company or product acquired by a big company is no guarantee. In fact it's oftne quite the opposite. E.g. Parse was acquired by Facebook, and then killed. Google has killed countless projects and companies. Oracle loves to kill products they acquire. The list is endless.

Re: Parse is shutting down today

#243

Post by pier25 »

hackerboos wrote: post #95
primitivesuave wrote: post #60

Earlier quoted context omitted.

I second the Firebase recommendation. Facebook killed off their BaaS acquisition while Google doubled down on theirs. If you prefer open-source, Horizon ( http://horizon.io/ ) is a great alternative to Firebase but does not have many of the key features like file storage and iOS/Android SDKs.

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

Re: Parse is shutting down today

#244

Post by reality_czech »

jerf wrote: post #137
mofirouz wrote: post #79

Earlier quoted context omitted.

Shutting down is not the same as failure

But it is a reasonable enough definition of it that we should be able to apply the principle of charity to calling it a failure, no? It is not something anyone would mistake for "success" on its own terms, even if the people involved did OK for themselves.

Parse is just "doubling down on its amazing bet." No failures here!

Re: Parse is shutting down today

#245

Post by cperciva »

flukus wrote: post #240
jasonm23 wrote: post #233

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. That said, I never used it, I saw it appear, had a look, decided what it offered was too rudimentary to be scalable, and moved on. That said, as an open source offering, it's quite interesting. This post answers the basic question, what is parse: http://blog.parse.com/ann…

> 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?

Re: Parse is shutting down today

#246

Post by nodamage »

hota_mazi wrote: post #241
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…

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

Re: Parse is shutting down today

#247

Post by grovegames »

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 ?

From my understanding, it provided services that you would have to create from scratch in your own infrastructure that would be a significant undertaking. For instance, push notification in iOS is a bit of a nuisance if your app really doesn't rely on a complex server back end, but you would like to still add push notifications. Parse did this portion for you, so you could focus on the product. I could be wrong though, I looked at it a year ago, and my memory isn't what it used to be.

Re: Parse is shutting down today

#248

Post by asdfaoeu »

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 ?

This seems like the best documentation http://parseplatform.github.io/docs/rest/guide/

From my reading it seems like a generic rest service. I suppose like COTS for rest services.

Re: Parse is shutting down today

#249

Post by biot »

vning93 wrote: post #116

I loved Parse from the time I first started using it in college. It started out as a really handy way to spin up small apps quickly so I could start beta testing my app quickly with real users. One of the main problems though was that it really felt like just a prototyping tool to me, and I never really used it for real apps in production. Thus, for my latest project that I've been working on for several months now,…

Does this support multi-tenant apps? Most BaaS products I've seen assume that your account is hosting a single application and every user has visibility into almost everything. Versus an account that is supporting n clients, and each client has zero visibility into the data of other clients, unless via whatever secure mechanism they've granted permission for client X to see something within their company.
Post reply on HN