{"id":100298,"date":"2021-05-27T16:22:46","date_gmt":"2021-05-27T14:22:48","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/opublikovana-subd-immudb-1-0-obespechivayushhaya-zashhitu-ot-iskazheniya-dannyh"},"modified":"2021-05-27T16:22:46","modified_gmt":"2021-05-27T14:22:48","slug":"opublikovana-subd-immudb-1-0-obespechivayushhaya-zashhitu-ot-iskazheniya-dannyh","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/opublikovana-subd-immudb-1-0-obespechivayushhaya-zashhitu-ot-iskazheniya-dannyh","title":{"rendered":"The immudb 1.0 database is released, providing protection against data distortion.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

A significant release of the immudb 1.0 database has been introduced, ensuring the immutability and preservation of all data ever added, as well as providing protection against retroactive modifications and enabling cryptographic proof of data ownership. Originally, the project was developed as a specialized NoSQL storage system manipulating data in key\/value format, but starting with the 1.0 release, immudb is positioned as a full-fledged database with SQL support. The project's code is written in Go and is distributed under the Apache 2.0 license. <\/p>\n

Data in immudb is stored using a blockchain-like structure, ensuring the integrity of the entire chain of existing records and preventing changes to already saved data or the replacement\/insertion of records in the transaction history. The storage supports only the addition of new data, without the possibility of deleting or modifying already added information. Attempts to modify records in the database only result in saving a new version of the record; the old data is not lost and remains accessible in the change history. <\/p>\n

Unlike typical blockchain-based solutions, immudb achieves performance levels of millions of transactions per second and can be used to run lightweight services or for embedding its functionality in applications in the form of a library.

\"The<\/center> <\/p>\n

High performance is achieved through the use of the LSM (Log-structured merge-tree) with a value log, which ensures quick access to records even during high data addition intensity. To maintain the integrity of the storage system, a hierarchical structure known as the 'Merkle Tree' is additionally employed, in which each branch verifies all underlying branches and nodes through collaborative (hierarchical) hashing. With a final hash, the user can verify the correctness of the entire operation history and the accuracy of past database states (the root verification hash of the new state is calculated based on the old state). <\/p>\n

Clients and auditors are provided with cryptographic proof of ownership and data integrity. The use of public key cryptography does not require the client to trust server<\/a>, and connecting each new client to the DBMS increases the overall level of trust in the entire storage system. Public keys and key revocation lists are stored in the database, and during encryption operations, Intel SGX enclaves may be used. <\/p>\n

The DBMS includes support for SQL, key\/value storage mode, indexes, database sharding, creating snapshots of data states, ACID transactions with snapshot isolation (SSI) support, high read and write performance, optimizations for efficient SSD usage, and support for operation in the form of server<\/a> and embedded libraries, REST API support, and a web interface for management. Typical applications where DBMSs like immudb are in demand include transaction processing with credit cards, storage of public keys, digital certificates, checksums, and logs, creating a duplicate storage for important fields in traditional DBMSs. Client libraries for working with immudb are available for Go, Java, .NET, Python, and Node.js. <\/p>\n

Key enhancements in the immudb 1.0 release: <\/p>\n