Scalar DB has its own data model and schema, that maps to the implementation specific data model and schema. Also, it stores internal metadata for managing transaction logs and statuses. This document briefly explains the Scalar DB data model, how data types are mapped between Scalar DB and the other database implementations, internal metadata, and how Scalar DB database schema can be defined.
The data model of Scalar DB is a multi-dimensional map based on the key-value data model. A logical record is composed of partition-key, clustering-key and a set of columns. The column value is uniquely mapped by a primary key composed of partition-key, clustering-key and column-name as described in the following scheme.
(partition-key, clustering-key, column-name) -> column-value
For each database implementation, there is an adapter that converts the database specific data model into the Scalar DB data model, thus; users usually don’t need to care about how it is converted and can design database schema on the basis of the Scalar DB data model.
Data type mapping between Scalar DB and the other databases
Here are the supported data types in Scalar DB and their mapping to the data types of other databases.
Internal metadata for Consensus Commit
Scalar DB (Consensus Commit) manages metadata (e.g., transaction ID, record version, transaction status) stored along with the actual records to handle transactions properly. Thus, along with any required columns by the application, additional columns for the metadata need to be defined in the schema.
It is a little hard for application developers to care for the schema mapping and metadata for transactions, so we offer a tool called Schema Loader for creating schema without much knowledge about those.