Quantum Ledger Database (QLDB)
You have probably heard terms like NFTs, DeFi, Quantum, Ledger, BlockChain, Digital Coins and others, but have you ever wondered how they are intrinsically related?
They are part of a new way to protect, validate and make unique anything that goes through it's management and control process. A decentralized process.
Part of this new world is the QLDB, where a new approach to how to store data is presented.
Thinking about chained related data, ensuring that your new state is securely linked to the previous state, and the entire chain of states can be validated, several proposals were presented.
The blockchain algorithm is one, where you create a genesis event, with date, initial hash, payload, and generate a hash that will be used as the preview hash of the next event, and thus chaining the data sequence securely.
Another aproach, from the persistence perspective is the QLDB. The basic idea behind QLDB consists of three different tables, so to speak, Journal, Current State and Index History.
The Journal would represent the blockchain concept in a similar way, but containing only the hashes (metadata) of the events, where the persisted hash is generated based on the inserted event, with this unique id equal to zero in the initial event of this chain.
The current state, which would house the last update information. His idea would be to optimize performance in the search for the most current information.
The index history, where it would present in chronological order in which the data was entered
Below, is presented a suggestion on how to implement the AWS QLDB straigh forward. For more details, please check references.
https://docs.aws.amazon.com/pt_br/qldb/latest/developerguide/what-is.overview.html
