Decentralized Database with Blockchain Attributes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional distributed database systems rely on a trusted master-slave architecture, where data consistency and security are managed by a single entity, lacking decentralized trust and blockchain attributes, which restricts flexibility and scalability in transaction processing and data replication.
Innovation Solution
A decentralized database system with blockchain attributes that allows incremental implementation of blockchain features, enabling immutability, tamper-resistant transaction logs, non-repudiation, controlled replication, and decentralized trust, while supporting rich transactional queries and maintaining data consistency across nodes through an ordering service.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a master-slave distributed database architecture is used, then data consistency can be maintained through duplication, but the system lacks decentralized trust and relies on a single trusted entity
Solution Approach 1:
The patent segments the centralized master database into multiple peer database nodes that each maintain copies of the data. Instead of one master controlling all slaves, multiple peers collaborate through consensus mechanisms, dividing the trust authority across the network rather than concentrating it in a single entity.
Solution Approach 2:
The patent introduces a consensus mechanism as an intermediary process that mediates between peer database nodes. This consensus protocol acts as a neutral mediator that verifies and coordinates data changes across the network, replacing the need for a trusted master entity while maintaining data consistency.
2Reliability
If blockchain attributes are implemented, then immutability and tamper-resistance are achieved, but system complexity increases
Solution Approach 1:
The patent implements multi-functionality by combining traditional database operations with blockchain consensus mechanisms in a unified system. The database nodes perform both conventional data storage/queries and blockchain-style consensus verification, reducing the need for separate specialized systems while achieving immutability.
Solution Approach 2:
The patent applies partial blockchain attributes selectively rather than implementing full blockchain functionality. It uses consensus mechanisms and immutable logging for critical data integrity operations while maintaining conventional database operations for routine transactions, avoiding the overhead of complete blockchain implementation.
3Productivity
If data is duplicated across multiple nodes, then performance at end-user worksites is improved, but ensuring all databases remain current requires additional overhead
Solution Approach 1:
The patent implements continuous data synchronization through the consensus mechanism that operates continuously across peer nodes. Instead of periodic duplication updates, the system maintains continuous coordination among peers, ensuring data remains current without interrupting ongoing transactions or requiring scheduled synchronization pauses.
Solution Approach 2:
The patent enables peer database nodes to autonomously synchronize data through the consensus protocol. Each node independently verifies and propagates data changes to other peers without requiring centralized coordination or manual intervention, allowing the system to self-maintain data consistency across the distributed network.
Data Source
AI summary
An example operation may include one or more of a processor configured to receive a database command from a client system, the database command comprising a database function and parameters to be used by the database function, and to execute the database command on database data, and an interface configured to transmit the database command to one or more other databases that are within a decentralized database system in which each database node is controlled by a different entity, wherein in response to receiving a request from an ordering node of the decentralized database system, the processor may commit results of executing the database command to a database and store information about the database command in an append-only immutable database log.