Backendless

In the software as a service (SaaS) landscape, there are many variations of “____ as a service”. We recently discussed API as a Service, and in this article, we will explain what mobile backend as a service, or MBaaS, means.

Does it makes sense for your app to be serverless? As with most development decisions, the answer is: it depends. What does serverless really mean? In this article, we’ll break it down for you.

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.

When working with Backendless, data you accumulate can easily be exported. The inner workings of the export process itself are quite complicated since it takes into account all the relationships within your data. For you, the user, this process is in fact quite simple.

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.

Backendless Console is a development tool that is also the frontend for your backend. It is quite common for more than one developer to need to access the Console to view data, test queries, or adjust the security settings. The Console and the backend are built in a way where concurrent developer logins to the…

In addition to the app development APIs, we also make available a very rich set of administrative and management functions. Every single feature available in Backendless Console is also available via specialized REST API. Whether it is performing a data import/export, setting up database schema, or retrieving application’s analytics – all of these can be…

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, security auditors, system administrators, and ultimately customers and the users of the app.

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…