In another Recipe article, we discussed how to load data from the Backendless mbaas server using paging. In fact, data paging is only one of the features available in the data loading API. In this post, we are going to show how to fetch data objects with sorting. The sorting option can be combined with…

In this article, we’ll consider some practical examples of how to use the Backendless Data Collection library to its fullest extent. You can find code documentation and sources for the library here.

Whether you develop with IntelliJ IDEA, Eclipse, or Android Studio, the Backendless library (jar) for Java/Android must be referenced as a dependency. The library includes all the APIs that provide access to the backend functionality. The library is deployed to the centralized Maven repository, which makes it easy to import it to any Backendless-powered app.

In a previous post, we described how to use the custom business logic code generator to create Backendless timer code. The previous post left off at the step when the Backendless Console created the code.

In a previous post, we wrote about Backendless server-side timers – blocks of code which run on a pre-defined schedule. A timer is a Java class and can be created by hand. The most tedious part is figuring out the scheduling definition. Currently, this is done by declaring the timer’s schedule through a JSON object…

Previously, we wrote about how to store and retrieve objects to and from server-side in-memory cache. Quite often when working with your cache, it is necessary to check if an object already exists in cache. Backendless provides an API for that function. The code below checks if an object exists in cache, and if not,…

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 post, we will show how to save an object with relations in Backendless Database. We are using the “code first” approach, which means we will not be creating data tables in the backend. Instead, the code will dictate to the backend what the data schema should look like.

Have you ever wondered why is it often so tedious so make your simple Java app a web server, with the methods becoming the endpoints? You need to add libraries, write additional “web” wrappers, set up a server and a hosting, configure load balancing and much, much more.