The data is accessed through the SDK as if it is a local database with a single data model from the programmers point of view.
All data is managed through the Database Platform as a Service — dbPaaS. Data storage, replication and redundance is provided as a service. No programming is required for setting up, managing or running applications within the database.
The data can be made available to multiple devices and selectively shared based on access control lists (ACL).
This enables seamless exchange of data between devices and cloud, including cloud to cloud. The database always makes sure that all connected clients are kept up to date.
Database containers may be setup to receive data and have the SDK listen to data changes similar to a queue or publish/subscribe service.
The flexible data model combines some of the features of more than one type of database. Mimics characteristics found in many different types of database technologies.
The ability to create a data model that includes relational data, key/value data, hierarchical graphs, objects, and streams, makes it possible to create a data model that matches almost anything.
CloudBackend supports containers that allow objects of any datatype to be stored within them, but containers can also be set to only accept objects of a certain datatype, and thus gets it schema assigned. The latter is similar to defining the columns of a relational table.
Datatypes are very flexible and user configurable. They define things like the icon for objects of a specific type, how the objects are visualized in lists and database queries, how they are previewed, and if any specific application should be invoked to process them.
