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

31–40 of 297 posts

Re: Parse is shutting down today

#31

Post by valgaze »

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

They did some extraordinary work

Very interesting interview with Parse founder in its heyday: https://soundcloud.com/heavybit/caveat-founder-ep-1-featurin...

On finding an interesting market @ 13:30: Evidently the Parse folks discovered they were dealing with an agency building an application for the Food Network. The agency needed SLAs/enterprise contracts and Parse found a $$ customer base

Re: Parse is shutting down today

#32

Post by jkarneges »

mofirouz wrote: post #24
rawrmaan wrote: post #13

Parse was an amazing discovery when I was just starting out my dev career and I've used it in all of my major projects, but it had some serious shortcomings. I wrote about why I think Parse failed from a developer's perspective. https://news.ycombinator.com/item?id=13522602

Why do you think Parse was a failure in the first place? Surely, Parse founders got a nice little cash out of the acquisition and Facebook got developers onboard and Facebook Login integrated onto many apps.

Well, he said "from a developer's perspective" ...

Re: Parse is shutting down today

#34

Post by barnaclejive »

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?

I have created a few apps using Parse.com, one of them successful enough to take the additional time/cost hit to migrate and host myself using the Parse-Server project.

The open source project is great and I appreciate the effort that went into making sure we didn't all get (totally) screwed.

Would I use Parse-Server for a new project? Probably not. The state of the BaaS options out there has changed/improved significantly since Parse.com was a thing.

Re: Parse is shutting down today

#35

Post by quaz3l »

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?

I used it for a new project I started 6 months ago. We've since transferred to AWS and a Express/Node.js project. However the Parse Server open source project is very well maintained and supported. I would recommend it for any quick prototype project you need a backend, but don't need it to do anything fancy.

Re: Parse is shutting down today

#36

Post by giarc »

imns wrote: post #33

Ah yes, the day that so many unsupported apps stop working.

As for iOS apps, I imagine Apple's new attempt to remove unsupported apps from the app store will result in many of these apps getting the boot soon.

I've already seen the notification when opening an app that it might perform slowly since it is not supported (or something along those lines).

Re: Parse is shutting down today

#37

Post by squid3 »

The open source Parse Server offers more benefits than hosted parse.com. Many of the benefits are outlined in this blog post: http://blog.parse.com/announcements/what-is-parse-server/ Whatever you are building with Parse Server, Nodechef can help you get there faster. https://www.nodechef.com/parse-server

Re: Parse is shutting down today

#38

Post by ruslan_talpa »

mmastrac wrote: post #26
ruslan_talpa wrote: post #23

Earlier quoted context omitted.

Just read all your objections to Parse. It seems to me that all of them arise from two core things - You don't have access to database that actually holds the data - The database is MongoDB which is quite young compared to MySQL/Postgres and can't do terribly complicated stuff The above two things as you said made Parse very inflexible once you get beyond prototype phase. I think i solved all of your objections in my…

That's really awesome! I'm glad to see you've also solved a lot of the req/s issues that Parse had too. If prototyping tools are done right, I think they are valuable and awesome.

Thank you for the praise, however i really want to stress that Sub0 (and PostgREST) are not prototyping tools only :)

It's true that you don't build api's with them the way you would with a more traditional stack but you can build real products with this a lot faster. This style of building APIs clicks faster with people that use (and trust) Postgres

Re: Parse is shutting down today

#39

Post by ebbv »

gamache wrote: post #16
ebbv wrote: post #9

The Parse folks seem to have handled this reasonably well but this is the perfect illustration of why building your own application around a third party service like this is not a pure win. There is a tradeoff and it can in fact bite you.

It's a shame so many people think of the Data Access Object design pattern as something only Java developers should be using. Using DAOs to provide database-agnostic access to your data takes a few moments more at first, but then when you need to move data from $DB_X to $DB_Y, there's a lot less wailing and gnashing of teeth. Mediocre link on the topic: https://en.wikipedia.org/wiki/Data_access_object

I'm not sure what your point is. Do you mean that if only people used DAOs then Parse shutting down wouldn't be a problem? It only encapsulates the problem. You still need to go through a process to switch from Parse to MariaDB or whatever else you switch to. You just don't have to rewrite your whole application.

I'm in favor of DAOs and use them myself but they don't have anything to do with what I was talking about.

Re: Parse is shutting down today

#40

Post by jtmarmon »

parseuser wrote: post #28

The export data feature has been broken for months — it’s stuck in the “waiting to begin…” phase. Is there plans to allow people to export their data? I’d like to get my data out, but both options for exporting data via the dashboard are broken. They also disabled the ability to contact them in regards to the export data functionality.

uhhh...sorry to say but I don't think you're getting that data out anymore.

>When your app is disabled, you will not be able to access the data browser or export any data, and your applications will no longer be able to access the Parse API.

Post reply on HN