Immudb, an open-source tamper-proof database can serve as the main transactional database for enterprises. Version 1.2 can rollback changes and have data expire with full transactional support for everyday business applications and compliant with GDPR, including its “right to forget” requirements.
There is no need to have Immudb running next to a traditional database anymore, as immudb now has full ACID transactional integrity compliance. Immudb provides full integrity of data, as well as compatibility with SQL and key/value making it possible to move data to immudb without having to make changes to applications.
Immudb is built on a zero-trust model: history is preserved and can’t be changed. Data in this database comes with cryptographic verification at every transaction to ensure there is no tampering possible.
This database can be deployed in cluster configurations for demanding applications that require high scalability, up to billions of transactions per day, and high availability. Support for Amazon’s S3 storage cloud ensures it will never run out of disk space.
Immudb is the first to accomplish this feat with patented technology, plus it can scale infinitely to whatever size is required. For the first time, users have the choice of using an immutable database for all their needs and that is significant at this time of heightened cybersecurity needs. Today, the tamper-proof database moves out of the specialty classification into the mainstream bringing all the benefits of trust and integrity.
Immudb is open-source software that is free for anyone to use and capable of protecting sensitive data for workloads that require the utmost in security. There have been more than 12 million downloads of immudb, you can find it on GitHub.
Real World Case Scenarios for Immudb Usage
- use immudb to immutably store every update to sensitive database fields of an existing application database
- store CI/CD recipes in immudb to protect build and deployment pipelines
- store public certificates in immudb
- use immudb as an additional hash storage for digital objects checksums
- store log streams (i. e. audit logs) tamperproof
- store the last known positions of submarines
- record the location where fish was found aboard fishing trawlers