Pre-validated Event Processing in Decentralized Databases
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing centralized databases face challenges in managing and validating events in a decentralized environment, particularly in ensuring the correctness and validity of events recorded in a blockchain or similar decentralized database.
Innovation Solution
A system that includes a receiver to receive event data, a storage area to store chaincode of a smart contract, and a processor to execute the smart contract. The processor determines if the event data satisfies an endorsement policy, sets an identifier corresponding to the event data's context, generates an event with the data and identifier, and submits it to a decentralized database for recording, where the identifier validates the correctness of the event's state.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If event data is recorded in a decentralized database without pre-validation, then the system maintains decentralization and distributed consensus, but the processing overhead increases and event correctness cannot be ensured
Solution Approach 1:
The system performs preliminary validation of event data by executing the smart contract associated with the event before recording it in the decentralized database. This pre-execution determines whether the event data satisfies the endorsement policy and generates a valid event, ensuring correctness upfront and reducing the need for extensive querying of peer nodes during commit operations.
Solution Approach 2:
The system introduces an intermediary validation mechanism that acts as a mediator between event submission and database recording. This intermediary layer executes the smart contract to validate event data against the endorsement policy, serving as a bridge that ensures correctness without requiring direct extensive querying of all peer nodes, thus reducing processing overhead.
2Reliability
If extensive querying of peer nodes is performed to validate events, then event correctness is ensured, but the processing time and computational resources increase
Solution Approach 1:
The system performs the validation action in advance by executing the smart contract and determining whether event data satisfies the endorsement policy before the event is recorded in the decentralized database. This preliminary execution eliminates the need for time-consuming extensive querying of peer nodes during the commit phase, significantly reducing processing time while maintaining validation reliability.
3Ease of operation
If a centralized database is used, then data management and control are simplified, but the system cannot operate in a decentralized environment
Solution Approach 1:
The system enables each node in the decentralized environment to autonomously execute the smart contract and validate event data locally before recording. This self-service approach allows each node to independently perform data management and validation tasks, simplifying control at the individual node level while maintaining overall decentralized operation, thus achieving both ease of operation and decentralized compatibility.
Data Source
AI summary
An example operation includes one or more of receiving event data from an entity, determining the event data satisfies an endorsement policy, setting an identifier that corresponds to a context of the event data, generating an event which includes the event data and the identifier, and submitting the event for recording in a decentralized database, wherein the identifier is used to validate that a state corresponding to the context in the event data is correct.