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

281–290 of 297 posts

Re: Parse is shutting down today

#281

Post by webmaven »

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 ?

I would call Parse a "Backend as a Service"[0], akin to Firebase[1]. "API as a Service" is more like Apiary (bought by Oracle) or Apigee (bought by Google).

[0] https://en.wikipedia.org/wiki/Backend_as_a_service

[1] https://firebase.google.com/docs/

Re: Parse is shutting down today

#284

Post by niutech »

jasonm23 wrote: post #233
trumbitta2 wrote: post #215

Earlier quoted context omitted.

And nowhere in there I was able to find what's Parse and what does the open-source Parse Server do.

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…

No, Parse was a Backend as a Service (https://en.wikipedia.org/wiki/Backend_as_a_service), like Firebase, Kinvey, Telerik Backend Services or Backendless.

Re: Parse is shutting down today

#285

Post by pier25 »

primitivesuave wrote: post #261
pier25 wrote: post #243

Earlier quoted context omitted.

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

> Querybase is in an experiment and not for production

Also since Firebase doesn't allow more than one filtering field with orderByChild(...) I'm guessing Querybase will do all the work on the client. This is less than ideal since the data has to be downloaded first.

Re: Parse is shutting down today

#286

Post by hackerboos »

pier25 wrote: post #285
primitivesuave wrote: post #261

Earlier quoted context omitted.

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

> Querybase is in an experiment and not for production Also since Firebase doesn't allow more than one filtering field with orderByChild(...) I'm guessing Querybase will do all the work on the client. This is less than ideal since the data has to be downloaded first.

Querybase is also making permutations of all the data you may wish to query. Needlessly taking up space on your server that will have to be retrieved. Wasted bandwidth etc.

Re: Parse is shutting down today

#287

Post by digital_ins »

nickpsecurity wrote: post #63
mcescalante wrote: post #4

I have seen a fair number of "abrupt" and poorly executed shutdowns on HN over the last few years, and although I don't use Parse, I feel as though the team did a good job sunsetting this over the last year. Thank you for the product, the open sourced version, and for not ditching your community! Best of luck to everyone who worked on the team

Yeah, that's pretty impressive. YC should consider making it a requirement of funding that the components go open-source if they shutdown without acquisition, etc. Aside from collective benefit, a future, YC startup might get a head start from their docs or components. They seem to fund multiple startups in the same market segments at times.

But Parse was acquired by Facebook. So this clause wouldn't apply.

Re: Parse is shutting down today

#288

Post by jkestner »

primitivesuave wrote: post #60
jeyoor wrote: post #44

Earlier quoted context omitted.

Which BaaS options are recommended now?

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.

I really like Firebase, but for specialized cases as others mentioned. The realtime updates are solid, and the iOS SDK at least is deep enough to let you dig into edge cases when needed (like, how many clients are listening to this node?). But I use it like an in-memory store to sync live data. Can't imagine having to use it like a full database - I use Parse for storing more permanent data across tables.

Re: Parse is shutting down today

#289

Post by alysson_b4a »

trumbitta2 wrote: post #215
gfosco wrote: post #2

During this year-long shutdown/migration process, the open-source and community maintained Parse Server is what most people switched to. Parse is yours now. https://github.com/ParsePlatform/parse-server

And nowhere in there I was able to find what's Parse and what does the open-source Parse Server do.

Parse.com was a BaaS(backend as a Service) acquired by Facebook in 2013. Using the platform was possible to build and host most of all your app backend(database, legacy code, integrations, Push notifications, send emails, social login, ...) and to integrate with your app front-end using the SDKs or even using a REST API. Parse Server is the open source version of Parse.com launched after the Parse shutdown announcement.

Re: Parse is shutting down today

#290

Post by jerf »

010a wrote: post #193
jerf wrote: post #137

Earlier quoted context omitted.

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.

People also die. By your definition, are all people destined to fail because we all die? Is no one worth remembering, or being called "successful"?

You posted that directly in response to a message that reminded you about the principle of charity.
Post reply on HN