Dbia is TDPnet's database.
DBia is a distributed database technology that is designed to operate on TDPnet, leveraging its unique networking capabilities. This technology is characterized by its specialized service providers, each playing a distinct role in the database's functionality and architecture. Here's a detailed description of each component within DBia:
Entia:
In-memory optimized table
This component functions as an in-memory table, primarily storing entities. Each entity in Entia is characterized by a unique ID, creation time, type, state, and data formatted in JSON. This setup allows for efficient access and manipulation of data, ensuring quick response times for database operations involving these entities.
Linkia:
Maintains relationships between entities
Similar to Entia, Linkia is also an in-memory table. However, its focus is on maintaining relationships between entities. These relationships are defined by attributes such as unique IDs, creation time, type, state, and the IDs of the connected entities, along with JSON-formatted data. Linkia is crucial for representing complex relationships within the database, making it an essential component for handling relational data.
Kronia:
A synchronization mechanism for the database
This component acts as a synchronization mechanism for the database. At specified intervals, Kronia sends "save" signals to both Entia and Linkia. These signals trigger the synchronization of data from the in-memory tables to persistent storage. This process ensures data durability and consistency, as it guards against data loss in case of system failures or other disruptions.
Meshia:
Meshia connect & forms mesh networks
The role of Meshia is to connect Entia and Linkia, forming a mesh network. This setup is pivotal for the scalability and ease of administration of DBia. Meshia also acts as a conduit for Kronia's signals, facilitating the synchronization process across the distributed database system.
In-memory optimized table
This component functions as an in-memory table, primarily storing entities. Each entity in Entia is characterized by a unique ID, creation time, type, state, and data formatted in JSON. This setup allows for efficient access and manipulation of data, ensuring quick response times for database operations involving these entities.
Maintains relationships between entities
Similar to Entia, Linkia is also an in-memory table. However, its focus is on maintaining relationships between entities. These relationships are defined by attributes such as unique IDs, creation time, type, state, and the IDs of the connected entities, along with JSON-formatted data. Linkia is crucial for representing complex relationships within the database, making it an essential component for handling relational data.
A synchronization mechanism for the database
This component acts as a synchronization mechanism for the database. At specified intervals, Kronia sends "save" signals to both Entia and Linkia. These signals trigger the synchronization of data from the in-memory tables to persistent storage. This process ensures data durability and consistency, as it guards against data loss in case of system failures or other disruptions.
Meshia connect & forms mesh networks
The role of Meshia is to connect Entia and Linkia, forming a mesh network. This setup is pivotal for the scalability and ease of administration of DBia. Meshia also acts as a conduit for Kronia's signals, facilitating the synchronization process across the distributed database system.