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.

In a previous post, we introduced Backendless CodeRunner – a debugging utility for custom business logic. Now that you can run your timer code locally using CodeRunner, we’d like to show how you can attach your IDE to the CodeRunner process and debug the code.

In other posts, we have described how to set up a sample Geolocation data set and how to retrieve geopoints using the API. The geopoints in your application would not be the ones from the sample data set, we used it only to make it easier to get started with Backendless Geolocation. Adding geopoints to…

The Logout API is a logical counterpart for the User Login API, described in an article here. The full documentation for the Backendless REST logout API can be found here. The logout step is not required for most apps given that the user session will expire automatically. However, some apps choose to provide the functionality, especially…

In a previous feature, we described how to manually create data tables in Backendless Console. In this post, we will show how to set up a data table schema.

The article that shows how to store objects in Backendless also demonstrated dynamic data table creation. That approach is called “code first” – where the code dictates the database schema.

In another post, we introduced the feature of server-side API event handlers – a mechanism for injecting custom business logic into Backendless. In this post, we are going to review the process of creating an event handler for User Service APIs using Backendless Console. The User Service APIs include user registration, login, logout, user update,…

There are two types of custom (server-side) business logic supported by Backendless – timers and event handlers. In my previous posts have reviewed the entire process of developing, testing and deploying timers. Now I’m going to focus on event handlers.

It is common with many applications for two or more users to try (or need) to log in simultaneously using the same user ID and password combination. Some applications allow it (for example, Netflix supports concurrent logins with the same credentials from different devices) while other apps restrict it.