14 ms·
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. ht
by gfosco 10y ago
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 https://github.com/ParsePlatform/parse-server
- eriknstr 10y agoSomething 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?
- barnaclejive 10y agoI 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.
- jeyoor 10y agoWhich BaaS options are recommended now?
- ma2rten 10y agoI haven't used it, but firebase is popular.
- mignev 10y agoYes it's google behind ... but you should rewrite the whole application. That's why I respect Facebook about their decision to opensource the Parse Server. The is the beginning of the Open Backend world. With Parse Open Source everybody will get Personal MBaaS :)
- primitivesuave 10y agoI 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/ 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.
- hackerboos 10y agoFirebase 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 https://t.co/xd1KUPc8xY
- bfrog 10y agoThey must be using something akin to Cassandra to require something like that
- pier25 10y agoYep data modelling and querying capabilities is a real deal breaker in Firebase. Something as simple as filtering by 2 or more values becomes ridiculously tedious. http://stackoverflow.com/questions/26700924/query-based-on-multiple-where-clauses-in-firebase http://stackoverflow.com/questions/26700924/query-based-on-m...
- primitivesuave 10y agoI completely agree that on its own, the querying functionality can be quite tedious for anything complex. I linked to this solution on the comment above as well: https://github.com/davideast/Querybase https://github.com/davideast/Querybase
- pier25 10y ago> Querybase is in an experiment and not for production Also since Firebase doesn't allow more than one filtering field with orderByChild(...) I'm guessing Querybase will do all the work on the client. This is less than ideal since the data has to be downloaded first.
- harrisreynolds 10y agoBackendless is a solid option: https://backendless.com/ https://backendless.com/
- jordangonen 10y agoScaphold (https://scaphold.io/ https://scaphold.io/) is a super neat BAAS built on GraphQL!
- george_batski 10y agoYou should try one of these BaaS Firebase Back4app Backendless
- Liveanimalcams 10y agobut we still got screwed and I still hate facebook because of it.
- Myztiq 10y agoI used to work at Kinvey, they've got a pretty good product geared towards integrating with whatever you've got to connect with. They have always been security conscious, even have HIPAA support now IIRC. Happy to answer any questions, or get some current devs there into the conversation to help out.
- quaz3l 10y agoI 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.
- gfosco 10y agoI think it depends on your level of expertise and the requirements of your project. Having Parse Server as something you can set up in a few minutes on a VPS and start building a client-server app is great. The integration via the various SDKs is incredible, and it takes a long time to build something like that out. All the available options have their tradeoffs, but I think having the source and an interested community is a great pro in the Parse column.
- alysson_b4a 10y agoErik, I recommend use Parse Open source to any kind of App project that needs a robust backend. It is awesome, simple to install and to maintain.
- BinaryIdiot 10y agoIt's geared towards legacy. I have used parse in 3 different projects (none of that was my choice, these were existing projects I had to take over) and I would NEVER recommend it for new projects. The way everyone seems to use it, in my experience, is giving the client credentials to manipulate the full database which is absolutely insane. Obviously this is not good practice but every single parse project I've gotten thrown into already did this and it was a significant amount of work to move it to be more secure and NOT do that. I think the way it's created makes it very, very easy to make bad security choices. It's also basically a RESTful CRUD. That's mostly it minus some, mostly minor, bells and whistles. You can already do this with about 20 different open source stacks very easily and you're not stuck using this parse technology. I can't articulate just how much trouble parse has given me. I even took an app and re-wrote its entire backend away from parse significantly faster than doing a handful of updates.
- ShaneWilton 10y ago> I think the way it's created makes it very, very easy to make bad security choices. I can sympathize with this. I work on a dynamic API security scanner, and the vast majority of the Parse APIs I've scanned have either used API keys with full read/write permissions on the DB, or have left the database in development mode, essentially allowing anyone with an API key to modify the schema of the database. Parse was a very cool product, but most setups I've seen didn't take advantage of the (sometimes hard to find) security features Parse provides.
- jkestner 10y agoLater versions don't let you easily give the client full access. You instead have to do it through Cloud Code (another facet of Parse), so the key never leaves the server. Not to disagree with your overall assessment. I'm generally wary of these swiss-knife frameworks - they're written for a particular use case in mind, and if your project doesn't fit that, you may go through contortions to get things working smoothly.
- BinaryIdiot 10y ago> Later versions don't let you easily give the client full access. You instead have to do it through Cloud Code (another facet of Parse), so the key never leaves the server. That's fantastic! I never kept track of which version(s) I worked on but I had transitioned one project from Parse to Parse Server and it was still able to work this way but I'm glad they made progress to try and force better security.
- ojr 10y agofor 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
- SmokyBourbon 10y agoMissing documentation: what the hell Parse is.
- mignev 10y agoHi Fosco ... Thanks to you @flovilmart and the other heroes who made this possible :) You guys are aweosme!
- marknadal 10y agoI second the sentiment that Parse has done a good job of shutting the platform down and giving users warning/notice. I hope the Open Source version takes off (looks like it has, with 12K stars!). As a shameless plug though, there are other Open Source alternatives though - we wrote a migration guide for ours: https://github.com/amark/gun/wiki/Migrating-from-Parse https://github.com/amark/gun/wiki/Migrating-from-Parse .
- alysson_b4a 10y agoAwesome Fosco! The open source community has already 12k+ stars on Github and is growing fast. Thank you for all the work and collaboration! You rock guys!!!!
- trumbitta2 10y agoAnd nowhere in there I was able to find what's Parse and what does the open-source Parse Server do.
- Groxx 10y agoHuh. 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.
- taneq 10y agoSo 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?
- bjacobel 10y agoI'd assume the main goal of the open-source Parse Server is to provide some support for previous users of Parse? Who would already know what Parse does. Attracting new users unfamiliar with the technology seems at best secondary ( and possibly, unwelcome) to the Parse Server community now.
- franciscop 10y agoThat 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 anything else.
- bjacobel 10y agoFiles 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/package.json#L71 https://github.com/ParsePlatform/parse-server/blob/master/pa...
- franciscop 10y agoThat makes sense, I would have put them in /dist though