presented Significant release of DBMS Immudb 1.0 that guarantees the invariance and preservation of all added data, as well as providing protection against changes in the back number and gives the possibility of cryptographic proof of possession of data. Initially, the project developed as a specialized NOSQL-repository, manipulating key / value data, but starting from release 1.0 ImmudB is positioned as a full DBD with SQL support. The project code is written in the GO language and distributed under the Apache 2.0 license.
IMMUDB information is stored with the use of a blockchain-like structure guaranteeing The integrity of the entire chain of available entries and does not allow you to change the already saved data or replace / paste an entry into the transaction history. The repository only supports adding new data, without the possibility of deleting or changing the added information. Attempting to change records in the DBMS only leads to the preservation of the new version of the recording, the old data is not lost and remain available in the history of the changes.
The use of cryptography in binding to client keys does not require a client confidence in the server to verify and confirm the possession of data, and the connection of each new client to the DBMS increases the overall level of confidence in the entire repository. At the same time, in contrast to the standard solutions based on the blockchain, ImmudB allows you to achieve performance at the level of millions of transactions per second and can be used to launch lightweight services or to embed its functionality in the application form of the library.
High performance is achieved due to the use of wood LSM (Log-Structured Merge-Tree) with the logging of values that provides quick access to the records at a high intensity of adding data.
To maintain the integrity of the repository, the tree structure “ Mercla Tree