Over the past few weeks, Facebook officially transferred control of Parse to the open source community. If you’re using Parse today, then there should be little change to you. If you’re a developer tracking these repos, please update your branches to https://github.com/parse-community. Our home is now at http://parseplatform.org, and all docs have relocated to http://docs.parseplatform.org
The Parse project has been fully community run for at least the past three months. Ever since Facebook announced the open source version of Parse server, we’ve added long awaited and powerful features such as:
- Live Queries, supported across all major client SDKs.- Multiple Database support, starting with Postgres in addition to MongoDB.- Flexible authentication models and no longer restricted to Facebook and Twitter.- New Class Level Permissions.
And so much more;
Parse is stronger open than closed.
We’ve seen a trove of companies offering hosting services around the open source project and we encourage the less tech savvy users to explore those if they aren’t comfortable with hosting their own solution.
The adaptable model implemented in Parse Server makes it easy to extend it, allowing the most experienced developers to tailor its behaviour to their needs. With adapters for file storage, authentication, databases, caching, etc., Parse Server is designed to adapt your needs as you scale and grow. We’re commited to expand that support in the future and remove bottlenecks that prevent you and your team to grow and scale.
We’re grateful to Kevin Lacker, Fosco Marotto, and the entire Facebook Parse team for this gift to the open source community.
I would like to also personally thank all contributors, on every repositories and in particular (but no particular order), Arthur Cinader, Tyler Brock, Natan Rolnik, Steven Shipton, Roger Hu, Michael Mimeault and many more. They have pulled a tremendous amount of work and dedication to the success of the project. This transition would not have been possible without them.
What’s next?
Over the next few weeks and months, we’ll develop a proper roadmap with the help of the community to understand your most pressing issues and assess what features you want to see in the long run implemented in the parse platform.
We’ll update all the repositories READMEs with the dedicated maintainers, or go-to persons to reach out if you have issues or questions.
Parse is a complex ecosystem, with many open source components, and can be difficult to maintain. We always welcome new maintainers. If you feel you’re up to the task and the challenge, feel free to reach out to community@parseplatform.org or open an issue on the repository to which you’d like to contribute.
We’re more commited to Parse than ever and now it’s yours.
Florent Vilmart, principal maintainer.
Hacker Noon is how hackers start their afternoons. We’re a part of the @AMIfamily. We are now accepting submissions and happy to discuss advertising & sponsorship opportunities.
To learn more, read our about page, like/message us on Facebook, or simply, tweet/DM @HackerNoon.
If you enjoyed this story, we recommend reading our latest tech stories and trending tech stories. Until next time, don’t take the realities of the world for granted!