There are two types of custom business logic (Cloud Code) scripts supported by Backendless – API event handlers and timers. In this post, we will review the latter. A timer is a server-side program deployed to the Backendless server infrastructure which is scheduled to run on a pre-defined schedule.

This is an introductory post for a very broad feature – injecting custom server-side logic into Backendless. There are a lot of smaller features in Cloud Code (also known as Custom Business Logic), but it’s worth it to start with a general overview.

This article applies to version 3 of Backendless. The versioning feature in the latest version can be achieved by cloning your application to create replicas for development and staging. As an application is progressing through its lifecycle, there are different teams involved in interacting with the app and its backend. These teams include developers, testers,…

In another post, we wrote about support for multiple environments for your apps’ mBaaS backend. These could include development, testing, staging and/or production. As your backend advances through those stages, an obvious question is how to migrate the backend’s data from one environment to another. Backendless provides a very advanced facility for backend migration between…

Previously we described how to use the Backendless Console to generate custom business logic code. In this post, we will describe one of the most amazing features in Backendless – an ability to debug custom server-side code on the developer computer before deploying it to the cloud. It would be very helpful for you to…

Previously, we wrote how to generate custom business logic code for API event handlers and how to locally debug your custom code. Now your code is ready to be pushed to the Backendless servers. Once it is out there, the Backendless infrastructure automatically handles scaling the code execution and routing requests to an instance available…

In a Backendless backend, you can restrict access to API operations and/or application data. A restriction may apply either to specific users or to roles. When a restriction applies to a role, it automatically applies to the users in that role.

There are plenty of use cases when mBaaS-powered applications must use a centralized mechanism for incrementing or decrementing a value. There are several approaches for maintaining a counter – some apps use a database, others keep it in the server-side business logic (Cloud Code).

Now that you know how to generate code for custom business logic timers (Backendless background jobs) and how to locally debug custom business logic, it is time to learn how to deploy that code to production.