Migrate from Parse to Jelastic Cloud

| June 2, 2016

Kemel ZaidanRecently Kemel Zaidan, evangelist at Locaweb, our Platinum Partner from Brazil, published a really exciting article about how to easily migrate an application from Parse to Jelastic Cloud Locaweb.

We've decided to share with you this great content and prepared the translated from Portuguese version. Find the source article here.

Go ahead and enjoy reading!

The Parse is a BaaS (Backend as a Service), very popular among developers of mobile applications that do not want to worry about building the backend for their apps. Due to its simplicity and low cost, Parse is quite popular among startups.

Users were excited when Facebook bought Parse in 2013, as the purchase seemed to guarantee the company's endorsement with a drastic investment in the expansion of the service to assure that it would have a long and prosperous life.

However, on January 28, 2016, Facebook announced the termination of service within a year, till 28 January 2017, leaving approximately 2.5 million users looking for a new option. As a compensation for this news, the server side source code was released, which allows users to migrate their data to another service platform.Migration from Parse to Jelastic

In this tutorial, we will demonstrate how to install a Parse server from scratch, so you can easily bring life to your projects or even migrate your backend directly from Parse to Jelastic Locaweb.

To migrate your application, be sure to check the information beforehand on this migration guide available by the Parse.

Environment Installation

Start the installation process by selecting a Node.js environment with at least one node on 4.2 version and another node with MongoDB 3.0. Select the minimum and maximum scaling limits and adjust the settings according to your requirements.Migration from Parse to Jelastic

Once the environment is installed, go to the Github repository Parse Server, copy the GIT server endpoint, and then deploy the application in the Jelastic panel. If you do not know how to make a deployment in Jelastic from a GIT server, watch the video instruction on TecnoPapo .

Don't worry, Jelastic will automatically download all NPM dependencies from the packages.json file. 🙂

Server Configuration

Once you have completed the deployment of Parse server, you must configure it. You can do this via SSH or through the panel. In the application's root folder, create a file called config.json and type configure the data of your application as it is shown below:

    "appId": "your_appId",
    "masterKey": "your_secretKey",
    "databaseURI": "mongodb://user:password@host.jelasticlw.com.br",
    "port": 8080

AppId and Masterkey attributes are required and accept any string. If you're migrating from Parse, it is necessary to apply the same parameters used on it.

The necessary data for creating your databaseURI, will be received in the confirmation email just after your MongoDB instance is created.

For Node.js applications on Jelastic, all incoming traffic from port 80 is automatically redirected to port 8080. So, you need to make requests using the default port 80 in order to access the service.

To test if everything works fine, start the application manually through SSH from application's root folder by typing:

 ./bin/parse-server config.json

If all goes well, you will see the following message:

parse-server running on http: // localhost: 8080 / parse

Now it's time to automate the application startup process. Simply modify the Start script on the packages.json file to include our config.json configuration file. At the end, the line should look like this:

 "Start": "node ./bin/parse-server config.json"

Saving Your First Object

In order to save our first object, we will use the REST API , but you can also use any of the available SDKs .

To do so, you can use a REST client or CURL on the command line.

curl $ -X POST \
   -H "X-Parse-Application-Id: YOUR_APP_ID" \
   -H "Content-Type: application/json" \
   -d '{ "score": 1337, "playername": "Kemel Zaidan", "cheatMode": false}' \

If all goes as it should, you will get a response like this:

  "ObjectId": "vjzk6SiDIp"
  "CreatedAt": "2016-05-17T19: 13: 15.534Z"

Now you can retrieve the object directly (be sure to replace the vjzk6SiDIp by the objectId which was received after your object has been created).

$ curl -X GET \
   -H "X-Parse-Application-Id: YOUR_APP_ID" \


"ObjectId": "vjzk6SiDIp"
"UpdatedAt" "2016-05-17T19: 52: 55.963Z"
"CreatedAt" "2016-05-17T19: 13: 15.534Z"
"Score": 1337,
"Playername", "Kemel Zaidan"
"CheatMode": false


I believe that Parse will continue to be developed, with or without Facebook's investments. Although the reasons for this end of service are not yet completely clear, it seems that Facebook will keep investing in the software, at least for some more time.

In addition, a large community is being created as a consequence of the source code release: many companies, that want to entice the current customer base, and developers who see the release of the source code as an opportunity to take the development into their own hands and evolve it according to their needs.

It will be pretty interesting to see the end of this story.

Installation of the Parse server is not such a difficult task, but there are some issues, that should be taken into account. Being forced to migrate the service causes a certain discomfort, but at the same time, you can continue to use it and even save a few dollars as a benefit.

To learn more about Jelastic Locaweb, visit the product pageYou can find the full list with detailed information about all our partners on Jelastic.cloud.