Parse is shutting down today • Hacker News Board

Re: Parse is shutting down today

#11

Post by gm-conspiracy » Mon, Jan 30, 2017, 5:01 PM UTC

mmastrac wrote: post #10

gamache wrote: post #8

Earlier quoted context omitted.

What's the shame in being a great prototyping tool? While it's not the right choice for everything in your stack, it's definitely one of the fastest ways to get a service or product off the ground. My company came out of a similar place with Firebase. The initial version of our product was written 100% against Firebase. This was absolutely a good choice when it was made, but -- surprise! -- two years later, we had to…

That's the problem. It wasn't a great prototyping tool. Great prototyping tools are fine. Parse was not a great prototyping tool. In my not-terribly-nuanced-opinion, it was a really nice GUI wrapped around a not-so-great shim on top of MongoDB. I don't have specific experience with Firebase, but I believe that from what I've heard from others using it, has a much better design that would survive much longer in the fa…

I tried to reply to your comment you just deleted.

Re: Parse is shutting down today

#12

Post by dbancajas » Mon, Jan 30, 2017, 5:02 PM UTC

can someone tldr us on what happened to parse?

Re: Parse is shutting down today

#13

Post by rawrmaan » Mon, Jan 30, 2017, 5:02 PM UTC

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

Re: Parse is shutting down today

#14

Post by helloanand » Mon, Jan 30, 2017, 5:05 PM UTC

Check out the Parse Migration Guide to migrate away without any downtime - http://www.parsemigrationguide.com/

Re: Parse is shutting down today

#15

Post by helloanand » Mon, Jan 30, 2017, 5:05 PM UTC

Migrate away from Parse without any downtime - http://www.parsemigrationguide.com/

Re: Parse is shutting down today

#16

Post by gamache » Mon, Jan 30, 2017, 5:06 PM UTC

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