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 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.
In this edition of Backendless Spotlight, we visit the Pacific Northwest where a group of local leaders has created an app to guide tourists through a historically significant part of Tacoma, Washington, known as Japantown.
Today we’re going to take another look at data security configurations in Backendless. In this article, we will talk about how to restrict direct access to your data via API and only expose your custom API endpoints.
In a previous article (How to Save an Object with All the Children in a Single Call to Server), we examined how to simply save an object model. However, Backendless custom services give us much more flexibility when it comes to saving objects.
This post will show you how to implement a kind of “expiration” for your data objects. The strategy is sufficiently abstract, so it’s applicable to any resource you need to expire, including files, logs, and so on. Since the database does not have any built-in expiration mechanism, we’ll have to implement it on our own. Fortunately,…