immudb release v1.2

immudb v1.2 is officially released and ships with some great new features!

Now, with full transactional support for everyday business applications, the open source immudb tamper-proof database can serve as the main transactional database for enterprises.

“There is no need to have immudb running next to a traditional database anymore, as immudb now has full ACID transactional integrity compliance,” said Jerónimo Irázabal, co-founder of immudb and lead architect.

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.

What’s new

The first tamper-proof database, immudb 1.2 now has the ability to rollback changes and have data expire.

Through this immudb is now compliant with the EU’s General Data Protection Regulation (GDPR), including its “right to forget” requirements.

The GDPR went into effect in 2016 in Europe to protect privacy and govern the transfer of personal data. It is also used as a model in other countries in the world.

Unlike other databases, immudb is built on a zero-trust model: history is preserved and can’t be changed. Data in immudb comes with cryptographic verification at every transaction to ensure there is no tampering possible.

Many of the features included in this release were requested and discussed by community members, to whom we’re grateful for all the interaction and contributions!

Features

  • Full Transactions support: full ACID transactional integrity compliance both at Key-Value and SQL layer.
  • Support for logical deletion and expiration of KV entries: forget about data entries by setting an expiration date or by using the delete statement.
  • Support for logical deletion in SQL: it’s now possible to use the delete statement to logically delete records.
  • Updates are now unconstrained: row updates can be performed for any data structure, overcoming the limit immudb had with secondary indexes.
  • support for TIMESTAMP SQL type: full timestamp support when creating tables and when performing queries at microsecond precision.

Minor changes

  • Fixes to JOIN with subquery
  • INNER is now default join type
  • Some improvements to error messages
  • switch to standard SQL syntax for aliasing
  • switch to standard SQL COUNT(*) syntax
  • suport SQL for: SELECT DISTINCT, NOT LIKE, IN, IS NULL, IS NOT NULL, basic CAST (for timestamp)
  • Secondary indexes with NULL values (breaking change for on-disk format in SQL layer)
  • New session-based connection method in client SDK
  • Initial support for golang sql stdlib

immudb

BUILT ON THE FASTEST
IMMUTABLE LEDGER
TECHNOLOGY

Open Source and easy to use in new applications and easy to integrate into existing application.

MOST POPULAR

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.