Contents Introduction Prerequisites Installation Supported Versions Quickstart Step by step guide Creating a Client User sessions Creating a database Setting the active database Traditional read and write Verified or Safe read and write Multi-key read and write Closing the client Contributing Introduction immudb-node implements a grpc immudb client. A minimalist API is exposed for applications …
First steps to use Python SDK for immudb — the blazing fast, open source immutable database Contents Introduction Prerequisites Installation Supported Versions Quickstart Step by step guide Creating a Client Introduction immu-py implements a grpc immudb client. A minimalist API is exposed for applications while cryptographic verifications and state update protocol implementation are fully implemented …
Release v0.8.0 – atomic multi-key operations, cryptographic root signing and new SDKs The release sets the basis to support complex use cases with an enhanced security model: Atomic multi-key insertion: all entries are applied or none. Built-in atomicity provides the support needed to deal with multiple entities or complex entities mapped into several keys. Cryptographic …
immudb is lightweight, high-speed immutable database for systems and applications. immudb is open source under the Apache v2.0 License. With immudb you can track changes in sensitive data in your transactional databases and then record those changes indelibly in a tamperproof database. immudb makes sure that not just the latest data, but the complete history of, say, your debit/credit transactions is …
Release v0.7.0 – multi-database support, more resilience, even better performance, improved documentation immudb is getting faster and stronger! This release brings new features, even better performance and more resilience to immudb! Summary of the most relevant points: Multi-database support (you can run many databases with one immudb server to separate data or to provide multi-tenancy) …
immudb is getting faster and stronger! The next release brings new features, even better performance and more resilience to immudb! All the details will be released in the official announcement of the release, but here are the most relevant points: Multi-database support (you can run many databases with one immudb server to separate data or …
Dear community. immudb has just been released as v0.6.2 Release v0.6.2 fixes some important bugs and has many improvements – we recommend updating to it Bug Fixes require auth for admin commands even if auth is disabled on server, do not allow admin user to be deactivated base64 decoding of passwords: now it requires the …
Dear community. immudb has just been released as v0.6.1 Release v0.6.1 fixes some important bugs and has many improvements – we recommend updating to it Changelog [v0.6.1] – 2020-06-09 Bug Fixes disallow running immuadmin backup with current directory as source immuadmin dump hangs indefinitely if token is invalid #283, immudb crash on dump of empty …
Dear community. We’re proud to announce the first Release Candidate of immudb! After months of hard work, the team felt immudb is ready for the open source community. We focussed on security, performance and also ease of installation and use. With the release candidate published, we’re really looking forward to get feedback. If you want …
Copyright © 2020, 2021, 2022 by immudb. All rights reserved.
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.).
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.
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.
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.
No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:
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.
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.
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.
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.
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.
We will also send you the research paper
via email.
Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain.
Please enter contact information to receive an email with the free trial details.
