Distributed Data Management

Introduction

About the Subsystem

The Distributed Data Management subsystem can persistently store various structured data of a single device and also supports data synchronization and sharing across devices. In this regard, you can seamlessly integrate distributed application data among different devices, ensuring consistent user experience in the same application across these devices.

  • Local data management

    This module allows you to store and access structured data on a single device. It uses the SQLite engine to provide the relational database (RDB) and preferences database. With these databases, you can persistently store and access app data using different models.

  • Distributed data service

    This service can synchronize data across devices, so that users can access consistent data on different devices. DDS isolates data based on a triplet of the account, app, and database. DDS synchronizes data between trusted devices to provide the cross-device data access capability.

Architecture of the Subsystem

Figure 1 Architecture

Directory Structure

Level 1 and 2 directories of the distributed data management subsystem are as follows:

distributeddatamgr/         # Distributed data management
├── appdatamgr              # Local data management
└── distributeddatamgr      # Distributed Data Service

third_party/                # Open-source software
├── flatbuffers             # flatbuffers code
└── sqlite                  # SQLite code

Usage

Local Data Management

  • Relational database (RDB)

    Some basic concepts are as follows:

    • RDB

      A database created on the basis of relational models. The RDB stores data in rows and columns.

    • Result set

      A set of query results used to access the data. You can access the required data in a result set in flexible modes.

    • SQLite database

      A lightweight RDB in compliance with the atomicity, consistency, isolation, and durability (ACID) properties. It is an open-source database.

  • Preferences database

    Some basic concepts are as follows:

    • Key-value database

      A database that stores data in key-value pairs. The key indicates keyword, and value indicates the corresponding value.

    • Non-relational database

      A database not in compliance with the atomicity, consistency, isolation, and durability (ACID) database management properties of relational data transactions. Instead, the data in a non-relational database is independent and scalable.

    • Preference data

      A type of data that is frequently accessed and used.

Distributed Data Service

DDS provides apps with the capability to store data in the databases of different devices. It uses the KV data model.

  • KV data model

    KV is short for key-value. The KV database is a type of NoSQL database. Data in this type of database is organized, indexed, and stored in the form of key-value pairs.

    The KV data model is suitable for storing service data that does not involve too many data or service relationships. It provides better read and write performance than the SQL database. The KV data model is widely used in distributed scenarios because it handles conflict more easily in database version compatibility and data synchronization. The distributed database is based on the KV data model and provides KV-based access interfaces.

Repositories Involved

Distributed Data Management subsystem

distributeddatamgr_appdatamgr

distributeddatamgr_distributeddatamgr

third_party_sqlite

third_party_flatbuffers