Parse Migration FAQ

If you have any questions about anything in this FAQ, please don’t hesitate to reach out to our support team!

Why migrate from Parse?

On January 28th 2016 Parse announced they’d be shutting down their service, leaving quite a few customers questioning where they’d be moving. Luckily we’ve worked closely with Parse on creating a MongoDB instance on our platform in several different sizes to fit any Parse customer’s needs.

With their help we’re able to transition any current customer from their platform to ours, and our support is ready to jump in if you have any questions about the process.

Why use ObjectRocket?

ObjectRocket’s MongoDB-as-a-Service makes it easy to deploy and run your database by providing a production-ready instance instantly, tools to automate operations, and a fully staffed team of engineers and database administrators so you can focus on your application. Here are the highlights:

  • Redundancy built in with automatic HA failover at the mongoD level, and redundant mongoS tier.
  • Our tech stack is optimized for MongoDB from the ground up, including PCIe flash-based infrastructure, high memory-to-disk ratios, and container-based virtualization.
  • We have the best MongoDB support specialists and DBA experts, bar none, and 24x7x365 support, whether you are a 5GB or a 5TB customer.
  • We have competitive pricing with price breaks as your data needs grow.
  • We offer both the standard uncompressed MongoDB storage engine, MMAPv1, and the newer compressed storage engine that shipped with MongoDB 3.0, WiredTiger. WiredTiger is most comparable to RocksDB, the compressed storage engine your app used at Parse.

Why do I need a Parse instance instead of your normal MongoDB instances?

Parse has specific requirements for a MongoDB database, outlined in their Parse Server Guide. We’ve set failIndexKeyTooLong to false, added SSL, and used WiredTiger instead of RocksDB.

Note

We also offer MMAPv1 in 5GB and 20GB sizes as smaller options, but Parse recommends inflating your disk usage by 10x if you choose a non compressed storage engine like MMAPv1.

What size instance should I choose?

This can be a difficult decision due to the compression available in RocksDB, which is the MongoDB storage engine that Parse used. Parse recommends choosing a plan that is 10x the size of the Data storage listed under Analytics in your Parse dashboard. The image below shows an example of what this looks like:

_images/parse_data_storage.png

Our Parse-tuned instances are available in quite a few different sizes to fit your workload. Plan sizes are 20GB, 50GB, 100GB, 250GB, and 500GB for our compressed instances using WiredTiger. We highly recommend using this option as it’s going to be the closest option to what Parse was using. We also offer uncompressed MMAPv1 instances, designed for smaller deployments, available in 5GB and 20GB.

Note

If you have any questions about what size to choose, we recommend reaching out to our support team.

How do I migrate to ObjectRocket?

We’ve written a thorough migration guide which outlines in detail how to migrate to our platform.

I’m following the migration guide, but I can’t get my database migrated over to ObjectRocket. What should I do?

Contact our support team and we’ll walk you through it!

What do I do if I need more space?

We offer automatic scaling for our Parse instances in 5GB increments as you reach the capacity of your current plan. You can set an alert for space usage based on a percentage of total space used in the settings page for each individual instance.

Where should I host my Parse API server?

As our MongoDB instances have ties to both Rackspace ServiceNet and AWS DirectConnect, we would recommend using Rackspace Cloud servers or an AWS instance in the US-East zone. Rackspace also offers support for AWS under our Fanatical AWS umbrella. Another option is Carina, which is a simple Docker container option.

What do I do without auto-indexing?

ObjectRocket has some of the best MongoDB DBAs, and was founded by a MongoDB master with support in mind. Our DBA and Support staff are more than happy to help review any slow queries and implement the indexes on your behalf! We’ll likely have a few more questions than you’re used to, but rest assured we’re very comfortable with code and gleaning the best possible performance from any query pattern.

Does ObjectRocket support the Parse Dashboard?

The Parse Dashboard is available to run alongside the Parse Server, but unfortunately we can’t host those for you at ObjectRocket. They should work just as you expect if deployed elsewhere.

Does ObjectRocket support Parse Push?

ObjectRocket only handles the MongoDB portion of the Parse server, but if you follow the instructions for enabling Parse Server Push Notifications you should be able to utilize that feature as expected.