Parse was one the biggest and successful mBaaS solutions on the market. They bid us farewell last month, and they decided to shutdown Parse service on January 28, 2017. As you can see on social media, developers using Parse for their mobile backend trying to find alternatives of that service.
There are two main options in this case:
- Moving to another hosted mBaaS solution
- Moving to your own Backend Stack
Moving to another hosted solution looks easiest way for most of the developers. There are plenty of these BaaS providers on the market and new ones are launching after Parse shutdown. No one knows that one day same thing could happen to these providers too.
As a team we always believed in ownership of critical components. With emergence of affordable platforms like DigitalOcean, Heroku, Azure and Amazon AWS, there is no reason to hold back from hosting and owning your own Data & API stack.
Options for moving to your own stack?
There are 3 options to own your own stack:
- With the help of Parse Migration Tools and Parse Server you could host your own Parse server.
- You could code your backend services with your own stack from stratch.
- Use API Plug to generate most of the endpoints of your REST-API in 5 minutes and add other business logic functions if you need in your preferred stack.
How to move from Parse with using API Plug?
Let’s move step by step.
- Parse allows to export your data as MongoDB or JSON files. So first you need to login your Parse account and select your app then click on App Settings Menu on the left.
- Then click on Export Data button to export end send an mail to your email account.
- After a while you will receive an email from Parse with your zipped exported data link.
- When you download and extract this zip file you will find all your collections on Parse in different JSON files.
- The next step is about your datasource. To host your own API you will need a MongoDB instance. You could also host your own MongoDB instance in a cloud VPS such as DigitalOcean, AWS, etc. or choose a (DBaaS) Cloud Database as a Service provider such mLab, Compose, ObjectRocket etc. We are skipping this step and assume that you have chosen an option from above and now you have set your MongoDB instance and uploaded JSON files that you have downloaded from Parse.
- Now it is time to generate your API from your MongoDB datasource with API Plug. First login into your API Plug account and if you haven’t created yet, start a new API Project. Then click to “Link your DB” button and enter your datasource connection credentials.
- If everything goes well you will see your endpoints list that auto-generated from your MongoDB collections. If you don’t want to customise endpoint you could continue to next generation step.
- There are couple of options for generating your REST API. You could choose any language & framework from this list and click on to Generate your API button.
- Voila! It’s done ! Now you could select your auto generated source code to continue selecting your deployment environment.
- You could download full source code and test on your localhost and deploy to your cloud server or you could use our auto-deployment methods to deploy to your favourite cloud server providers such as DigitalOcean, Amazon, Heroku etc with a few clicks. There is also API Plug Sandbox deployment option to test your API without any deployment procedures.
- (OPTIONAL) API Plug Sandbox allows you to test your API immediately after you generate. It has some rate limitings because of being sandbox enviroment but you could use it while you are continuing your development process. You can choose a unique url for your api sandbox to access it and you are ready to live.
- You will be also have an auto generated API documentation ready. You can access it from Documentation menu. If you have sandbox deployment you could directly test your endpoints from your Swagger Documentation.
Now you could click here to start Using API Plug for creating your own API.