Live data from Hacker News

Parse is shutting down today

status.parse.com

171–180 of 297 posts

Re: Parse is shutting down today

#171

Earlier quoted context omitted.

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

Do you have any nontoy examples of this? I.e. nontrivial apps in heavy use.

Since it's in private beta which started a few weeks ago there is not specific system in production of Sub0 specifically, but someone (medical research institute with lots of research data) is already building a React frontend over their massive Postgres database using Sub0 and so far it's going well. The tutorial i provide explains building a complete API for something like Trello At the core of the system sits PostgREST and you can see a few users here http://postgrest.com/en/v0.4/intro.html#in-production although i suspect a lot more people are using it but don't advertise it. I've also done extensive performance test for speed, those numbers on the home page are real :)

Re: Parse is shutting down today

#172

Earlier quoted context omitted.

Did you vocalize any of these issues anywhere? I have never used Parse but have been looking at the open-source version. What are the many, many glaring bugs and problems you're referring to?

We would all go crazy trying to report all the bugs we found in every piece of software out there these days. When there are too many or something is too difficult to use, you move on. To a large extent, finding bugs is the responsibility of the developers. When users submit bug reports, good ones at least, they should be thanked. My point is, as a developer, you can't blame the users for not reporting bugs.

That wasn't my question, but ok. I was just asking for the list of the "many, many glaring bugs" that OP was talking about. He edited his link, though, so it's already been answered.

Re: Parse is shutting down today

#173
post #162

This is a real bummer. I am not a programmer by profession (I am a PM), but I took time to learn Parse from scratch to quickly write my own app. I managed to launch my app on App store and everything was well till Parse announced their shutdown. Unfortunately, with a 1 yr old at home and a demanding work / commute, I didn't really have the time to learn about their migration guidance or educate myself on a new platfo…

If you have some time and are looking for something easy check out Proxima:

https://www.jamroom.net/proxima

It's really designed for someone that is not a developer first. I built a MBaaS quite a few years ago, and Proxima was something I built on the side since I wanted an easy backend to power my own app. I also wanted someplace to do documentation, support, newsletters, etc. - so the idea with Proxima is that you can focus 100% on JUST your app and Proxima will handle your backend/website, etc.

Note too that it's not a SaaS - you would download and install it on your own server (although we do offer the hosting as well if interested). It's open source and free, so check it out if you're looking for something easy. Feel free to contact me as well if you have any questions.

Hope this helps!

Re: Parse is shutting down today

#175
I have ran several products on Parse over the last couple years. Loved it and was willing to pay. If you have all your data you can easily spin up a clone on Sashido.io and use them (they host the open source Parse for you and handle scaling and everything). I've migrated a few apps and other than some Parse SDK version upgrade compatibility issues, Sashido has been amazing. One complaint about Parse was customer support, Sashido has gone above and beyond in multiple instances already when it comes to response time AND knowledge. Highly recommended!

Re: Parse is shutting down today

#178
While the Parse team did an excellent job open-sourcing the platform and providing ample notice, it was still a costly learning experience.

Seamlessly transitioning a large user base on iPhone and Android to our self-hosted Parse with minimal service interruption or missed push notifications required significant engineering and coordination. The transition involved more hours than the initial build.

While we did our best (email campaigns, push notifications, etc.) we still have a sizable number of users who use the app daily, yet haven't updated it and are still pointing to (the old) Parse. We didn't plan on Parse going away back then, so those are not graceful failures.

Users who did update the app were signed out (couldn't maintain the session in the switch), resulting in a lot of "I didn't get my forgot password email" questions to support and an unknown number who won't bother troubleshooting it.

With the information at hand over a year ago, I still would have went with Parse. It really did help us get off the ground quickly. Maybe we would have missed our window of opportunity without it.

Re: Parse is shutting down today

#179
Since Parse announced the final of service as itselve, we were finding an option as easy as Parse is, so we found SashiDo, great solution our apps are on track again. They give us a great and proactive service.

Hernan Mejia SECUOIA CEO

Re: Parse is shutting down today

#180

So the alternative options are: - pouchDB - https://github.com/pouchdb/pouchdb - RxDB - https://github.com/pubkey/rxdb - gunDB - https://github.com/amark/gun - horzion - https://github.com/rethinkdb/horizon - firebase - https://firebase.google.com/

Kind of strange that you just threw in RxDB (your own creation?) and GunDB (which is easily torn apart as snakeoil whenever it appears on HN) along with the rest of them.
Post reply on HN