[deleted]
Parse is shutting down today
201–210 of 297 posts
Re: Parse is shutting down today
#202So we know there is a Go version somewhere I wonder why they didn't opensource this instead of rewriting everything to nodejs...
Re: Parse is shutting down today
#203A few points on our parse.com and migration to parse-server experience: - I didn't like it initially. Not only the name (parse what?) but also because people started using it as a relational storage, which it clearly were not. Later, I became one of them (got convinced by colleagues). - We recommended parse.com to a few clients, and they really enjoyed it. - Had some issues with SDKs but we've been able to workaround…
I know sales pitches are frowned on here but in the interest of helping out (with probably no return based on most users' Parse instance sizes), I have to share this. We were in the same boat when Parse shut down so here's just another option for anyone looking to migrate their app away still.
We took the parse server and built a hugely scalable platform on AWS and made it free to signup. We're still adding features but if anyone wants to start using it, it's in Production and available via http://octobas.com
You can also migrate your app to any externally hosted MongoDB service (like mlab.com) and simply connect your MongoDB instance to an Octobas.com Parse Application. (still for free under the base plan.. this method actually works out even cheaper when you scale up).
Re: Parse is shutting down today
#204I've spent the last 15 minutes on parse.com, github.com trying to find out what the parse backend actually is. Can someone explain?
Parse was a backend as a service that allowed for a cloud hosted database to be connected with web and mobile apps with simple JavaScript. It was a lovely tool for hackathons. They could also run arbitrary JS in response to events at scale. It competed with Firebase until they were acquired by Facebook.
It all makes me feel very stupid. I did programming since childhood and web since the beginning, I was clouds (virtualization) user even before millennium, I do backends for a living, saw a lot of JS code, know something about mobile apps, but I must join this thread.
"Parse Server is an open source version of the Parse backend that can be deployed to any infrastructure that can run Node.js" - each of these words one-by-one do have some meanings, but altogether they have none, neither your explanation for me. I fully believe it's totally my fault and it's hopeless, so please no reply.
Re: Parse is shutting down today
#205Sashido is the best alternative of Parse.
Great service and outstanding support.
Re: Parse is shutting down today
#206Sashido is the best alternative of parse.
Great Service and outstanding support.
Re: Parse is shutting down today
#207Earlier quoted context omitted.
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?
It'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…
> 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.
Re: Parse is shutting down today
#208Earlier quoted context omitted.
It would only if the software source or patents compromised the value they gained from the business. This would be the case for some startups. It wouldn't be for others where brand, talent, & existing users were what they were after. It also wouldn't take any significant time given developers could just push the final source and docs into a Github repo with a license. Or just dump it as a zip on the web. That's nothi…
How many production systems have you come across that could be dumped onto the public without any cleaning? Credentials, build systems, personal information, patent use, are a couple of examples that I've seen in prod code that couldn't or shouldn't be included. Assuming the cost of open sourcing something is zero, even if it's just a zip dump, is usually not correct.
Fair enough. I forgot about the malpractice of putting credentials and personal information in the code itself. Companies doing that would have a hard time open sourcing the code. Others whose build system doesnt cleanly separate 3rd party or internal stuff might also have trouble. Patents I already handled by saying they simply don't release third party stuff that's proprietary. Patent-encumbered code or tech is one such thing.
So, yeah, I'll take those corrections.
Re: Parse is shutting down today
#209So we know there is a Go version somewhere I wonder why they didn't opensource this instead of rewriting everything to nodejs...
Assuming this is true, probably due to the fact that most apps using Parse are already in Javascript.
Re: Parse is shutting down today
#210I would like to make an appeal. Let's use this post as a great recognition for the Parse team hard work and share also our lessons learned using Parse/Parse Server as a Backend. Thank you, Thank you guys. @csmajorfive, @gfosco, @laker, @HectorRamos,@jamesjyu, @flovilmart ... and everyone else
Thanks for the shout out!