Pointer Permissions were launched last June as a powerful new way to secure your app without needing to change your code or database. For many extremely common patterns like messaging and profiles, Pointer Permissions are the easiest way to secure your app. Pointer Permissions are now also available in the latest versions of the open source Parse Server and Parse Dashboard.
Here at Parse, we are big fans of open source software and the communities which form to build things together. Parse Server, released just 47 days ago, has already seen 50 contributors join the team. It’s incredibly exciting to see this project moving so quickly, with new features being added along with many improvements and fixes. We’ve been open-minded to suggestions, and have favored accepting contributions over enforcing too many rules. The Parse eco-system is yours now, and it’s very important that you feel some ownership.
There are a lot of options out there for hosting your Parse MongoDB database. In our migration guide we recommend that customers without database administration experience choose one of the hosted MongoDB providers such as mLab or ObjectRocket.
Here at Parse, we believe in open source as a way of accelerating innovation, learning from our community, and collaborating on scalable solutions to hard challenges in mobile development.
Dealing with concurrency and reentrancy is one of the more difficult challenges any library will inevitably face as it grows. Here at Parse, we have put a large effort towards ensuring that anything you do with our SDKs is thread-safe, without letting performance suffer.
The Cloud Code environment is the fastest way to get some dynamic application logic running online. But as your app grows, you may want more features, like the ability to use arbitrary node.js modules or to test things locally. The Parse Hooks API makes it possible to use your own node.js server in conjunction with Parse, and today we’re launching functionality to make it even easier.
If you saw Charity’s post back in April, you’ll recall that Parse is using MongoDB built on RocksDB (“MongoRocks”) in our production MongoDB deployment. MongoRocks combines the MongoDB storage API and RocksDB storage engine to deliver faster writes and more efficient storage utilization compared with MMAP. At Parse we’ve seen write speed improvements of up to 50x and up to a 90% reduction in disk space. As we have hardened operations and tooling around MongoRocks deployments, we’ve found another great advantage: it can make doing full and incremental backups incredibly easy!
There’s really nothing like getting an idea on Friday, and having a working prototype by Monday. Many companies are started this way, and it’s what brings tens of thousands of people to hackathons every year. Parse does an incredible job in this space, offering a host of services which are easy to integrate. I want to tell you about how I built a fully-realized MVP last weekend using Parse, Heroku, and Twilio, while fitting in an overnight vacation to Santa Cruz.
The Parse SDK has been and continues to be an important part of mobile development on Parse. As Parse developers, you’ve already gotten to know the Parse SDK from its public API, but today we open sourced our SDKs so you’ll finally be able to take a peek at its inner workings.
It was awesome to see how many of you were interested in our recent blogpost on moving our API stack from Ruby to Go. In fact, it’s one of our most visited and commented on posts, ever. We also blogged about some of the libraries we used. Earlier this month, Parse engineer Abhishek Kona spoke about how we tackled this at Gophercon. Enjoy this deeper dive into a fun project.