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

191–200 of 297 posts

Re: Parse is shutting down today

#191

Post by ojr »

eriknstr wrote: post #25
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

Something I've been wondering is would you recommend using the open source Parse server for new code or is it more targeted towards projects that were already using the Parse API?

for mvp I would say yes, parse-server provides security (ACLs/permissions) and performant database query helpers out of the box, its a battle-tested abstraction layer to mongodb, I had to make some workarounds to work for my specific usecase but just like any other framework it has it pros and cons, marketing and getting new users is the bottleneck for me not the database

Re: Parse is shutting down today

#192

Post by bfrog »

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

They must be using something akin to Cassandra to require something like that

Re: Parse is shutting down today

#193

Post by 010a »

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.

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

Re: Parse is shutting down today

#195

Post by desireco42 »

While I know there are people who say they loved their Parse experience, I suffered greatly. There are bugs, there are issues, there are simply things that either don't work or are very hard to make work.

On top of it, architecture of the app I was trying to make work, was... challenging.

Anyhow, not a big fan, but it is open source and now you can fix those issues if you care about them.

Re: Parse is shutting down today

#197

Post by desireco42 »

st3v3r wrote: post #53
dbancajas wrote: post #12

can someone tldr us on what happened to parse?

Facebook bought it. Parse was highly coupled to AWS at the time. They spent some 3 years trying to get it to run on Facebook's cloud, and apparently failed to do so. Facebook decided to cut their losses, and shut it down.

Parse is not that challenging that you can't reimplement it in any platform you choose, especially in 3 yrs.

Re: Parse is shutting down today

#199

Post by [deleted] »

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.

[deleted]

Re: Parse is shutting down today

#200

Post by rogerthis »

A few points on our parse.com and migration to parse-server experience:

- I didn't like it initially. Not only the name (parse what?) but also because people started using it as a relational storage, which it clearly were not. Later, I became one of them (got convinced by colleagues).

- We recommended parse.com to a few clients, and they really enjoyed it.

- Had some issues with SDKs but we've been able to workaround them with the help of parse's team (pre and post FB acquisition).

- When the shutdown news came, that was a crossroad. Open source parse-server had got too many issues and we decided to postpone and not follow the recommended timeline. By august, we decided to stick to the open source version, but still no decision on using a third-party provider for the parse-server, mongodb, both, etc, etc. Also, the providers we had seen then turned the yellow light on due to the shutdown experience. By october, it was decided to follow the dark path of going on our own. For clients, we helped them on specific needs.

- The migration consisted of very minor changes in the "cloud code" part, and almost no changes at all to client apps. Difficult part will be to scale our infrastructure when needed.

BTW, we finalized the migration of our own app on saturday.

Post reply on HN