We are thrilled to unveil a groundbreaking feature that is set to transform the way you design databases – welcome to “Schema AI”! At Backendless, we continually strive to innovate and streamline the app development process, making it more accessible and efficient. Schema AI is our latest step in this journey.
All Backendless apps have the ability to add a single custom domain for app hosting and API endpoints. Now, you may add additional custom domains to your application.
The Deep Save API leverages the capabilities of the Transaction API to allow you to save related data objects in multiple tables simultaneously within a single API call.
In 2020, we released the Transaction API as one of our built-in API services. The purpose of transactions is to protect your data from partial database updates that fail to complete. The Transaction API is now available for Codeless.
The Backendless European Union Hosting Cluster is a server cluster located in Europe. This new cluster provides Backendless Cloud developers outside of the United States a faster serverless app hosting alternative.
UI Bakery is a no-code web app builder that enables users to “build cutting-edge solutions following a front-end first approach”. When you integrate a feature-rich no-code Backendless backend with your UI Bakery frontend, you get a visual relational database, user management, bulletproof security, highly-scalable serverless hosting, and much more.
AppGyver describes itself as a “professional no-code platform, enabling you to build apps for all form factors, including mobile, desktop, browser, TV and others”. When you integrate a feature-rich no-code Backendless backend with your AppGyver app, you get a visual relational database, user management, bulletproof security, highly-scalable serverless hosting, and much more.
Backendless Database now supports the JSON data type, a significant innovation that allows us to support both structured and unstructured data.
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.