With the Transactions API, Backendless Database can execute multiple database requests grouped into a single transaction. When any one of these grouped database operations fails, the entire transaction is rolled back – meaning any other changes within the same transaction are canceled.

As a developer, you often need to run a test query or send an API request to see the server response. Our REST docs show examples using curl, but that may not always be convenient. You may need to play with the API request arguments, change the body, etc., and modifying your curl command is…

Custom API keys may not seem like the most exciting feature of Backendless, but the flexibility that they provide is extremely valuable. In this article, we are going to take a closer look at this unheralded feature.

In Part 2 of our series, we are going to continue design backend for our Social App. So, the task for today is to implement such parts as Likes and Comments. You will see how easily you can reach this by using Backendless.

There are a lot of social applications around the world, such as Facebook, Twitter, WhatsApp, Instagram, etc. If we take a look under the hood, however, we can see they all share pretty standard features. For instance, we can’t imagine an app without the ability to establish relationships between users, or without “likes” and “comments”…

GraphQL is a powerful language that allows you to extract data from your backend via a single endpoint that can take complex queries and return data in a structure that is appropriate for the client. In this article, we will create a simple application to manage articles. For API, we will use the GraphQL implementation…

In order to discuss what API as a Service is, we must first understand what APIs and API Services (and microservices) are. In this article, we are going to explain these terms in the simplest form possible so that you can better understand how APIs fit into your business needs.

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.

Sometimes (or in some cases, every time) when you invoke a custom API Service, you may need additional information about the context from which the HTTP request was sent/received, such as user or device information. To collect that information, we provide a class called InvocationContext.