I thought it was devestating at first but I found solace when they went open source. But after stumbling across sashido.io i don't even miss parse.com sashido has the Same service but with better features although they still did not add the export feature to CSV. Which is really useful
Parse is shutting down today
251–260 of 297 posts
Re: Parse is shutting down today
#252I thought it was devestating at first but I found solace when they went open source. But after stumbling across sashido.io i don't even miss parse.com sashido has the Same service but with better features although they still did not add the export feature to CSV. Which is really useful
Re: Parse is shutting down today
#253Earlier 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 ?
The first iOS app I built used parse for the entire backend. We basically used it as a database in the cloud accessible by multiple clients (it can accommodate fancier uses as well). We didn't really run any custom code on the server side, Parse basically provided access to a shared db across our client instances. It allowed us to build a simple location sharing app in a few hours.
Re: Parse is shutting down today
#254During 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
That cannot work at all!
See inside /bin/parse-server:
require("../lib/cli/parse-server");
However there is no /lib folder, apparently its name is /src. So there is basically no possible way that is even able to run. How is this possible? Either someone linked /src to /lib (doesn't make sense) or they changed the name of the folder and didn't change anything else.
Re: Parse is shutting down today
#255Found this on the Parse CEO's LinkedIn profile[1]:
"Facebook acquired the company for ~$100m in April 2013, intending to build a business akin to Amazon Web Services, and we operated for two years as a semi-independent subsidiary.
Facebook ultimately chose to exit the hosting business but Parse continues to thrive as an open source project with official support at Amazon Web Services, Microsoft Azure, Google Cloud Platform, etc."
Was this widely reported? I never knew that the internal plan with FB's Parse acquisition was to build an AWS competitor. Kind of interesting!
I guess it was viewed as a hedge in case the FB on-platform advertising revenue didn't grow as fast as they were predicting.
Re: Parse is shutting down today
#256During 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
That cannot work at all! See inside /bin/parse-server: require("../lib/cli/parse-server"); The same with the package.json, it points to /lib/index.js . However there is no /lib folder, apparently its name is /src . So there is basically no possible way that is even able to run. How is this possible? Either someone linked /src to /lib (doesn't make sense) or they changed the name of the folder and didn't change anythi…
Files in src/ are run through Babel and output to lib/ as a prepublish step. The version that you download from NPM contains a lib/ directory.
https://github.com/ParsePlatform/parse-server/blob/master/pa...
Re: Parse is shutting down today
#257Earlier quoted context omitted.
And nowhere in there I was able to find what's Parse and what does the open-source Parse Server do.
Huh. Yeah, I dove around a bit, browsed the wiki, etc, and so far all I've seen is the equivalent of "an open source version of the Parse backend". No description anywhere that I can see about what it does or why you should care (unless you're already on Parse, of course). IIRC the Parse homepage used to have this, but ever since the shutdown notice (so, for the past year) the homepage has largely been useless.
So many posts on HN are like this, assuming that every obscure webservice is common knowledge. "Jabberwocky has reached version 1.1! Performance increased by 30%, users must migrate from 1.0 by the 12th. Use Jabberwocky in your business now! New users get a free trial!" OK that's nice but what tf is it and why should I care?
Re: Parse is shutting down today
#258Earlier 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 ?
It was basically a CRUD API as a service; simple object storage and retrieval via HTTP, with goodies like validation and nested routes (joins) and such built in.
Re: Parse is shutting down today
#259Found this on the Parse CEO's LinkedIn profile[1]: "Facebook acquired the company for ~$100m in April 2013, intending to build a business akin to Amazon Web Services, and we operated for two years as a semi-independent subsidiary. Facebook ultimately chose to exit the hosting business but Parse continues to thrive as an open source project with official support at Amazon Web Services, Microsoft Azure, Google Cloud Pl…
[deleted]
Re: Parse is shutting down today
#260Earlier 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
I wouldn't call this an "issue" as much as a "limitation". Just as you can develop a data denormalization process for any use case, you can develop one for Firebase.
Here's a practical example of doing joins with Firebase (written by David East who is also the star of that video you linked): https://github.com/davideast/Querybase