Backendless Support

Support for development, testing, staging and production environments

As application is progressing through its lifecycle, there are different teams involved in interacting with the app and its backend. These teams include developers, testers, security auditors, system administrators ultimately customers and the users of the app. 

Traditionally, application goes through the stages of development, testing, staging and production. Each stage has its own group of users.

It is vitally important that each stage has its backend with all the data, security policies and business processes in an isolated from other stages environment.

Backendless Service Platform provides support for multiple app environments through a feature called Versioning.

When an app is created, the initial version is called v1. Technically, it is the development stage and if you plan to run multiple environment, it might make sense to rename it to "development" following the steps described below:

  1. Login to Backendless console, select an app and click the Manage icon.
  2. Click the Versioning menu.
  3. Type in development in the Version URL Prefix text field and press Enter 

The version name always corresponds to the URL prefix, as a result, when it is changed, it must be reflected in the API calls. The version name is used in the endpoint URI for the REST clients and in the app initialization call for all other client types.

To create additional environments, such as testing or staging a developer should follow the next steps:

  1. Using the same screen as shown above, click the Add New Version button.
  2. Type in the name of the version (Version URL Prefix) and click the Save button.
  3. A version is created and can be used immediately: 

Using this approach it is possible to create as many environments as it is necessary for an app. The version/environment name provides all the required isolation between the data, users, security policies, messages, media streams and geolocation data.

Is article helpful?