immudb-on-arm


immudb support for ARM architectures

It’s exciting to learn that more and more projects are using immudb as their core immutable data storage. Different projects also mean different deployments and requirements.
One of the latest requests we received, is the support for ARM architecture. Besides running immudb on ARM server hardware, some IoT projects are looking into smaller systems as well, like a Raspberry Pi.

Reason is, that IoT produces a lot of sensor data that are the being used to make decisions. Therefore, it is important to to store that data at least for a certain amount of time, tamperproof.
Most IoT and embedded systems run on ARM, MIPS or RISC-V architectures.

As ARM is the most popular platform, we started to compile and test immudb for ARM architecture and want to share the good news.

ARM 64-Bit

immudb is written in Go and designed to run on 64-Bit systems. That made it very straighforward to compile it for ARM systems.

Simply clone the immudb repository on your system (best to have a Go development environment there as well) and run:

GOOS=linux GOARCH=arm64 make immudb-static

You can copy and run the immudb binary on your ARM 64 Bit system (Linux in the example above):

ARM 32-Bit

ARM 32-Bit

32-Bit wasn’t part of our initial design, but it didn’t took us long to make it 32-Bit ready.
For now you can find the 32-Bit version in a separate branch, but that is going to change soon.

https://github.com/codenotary/immudb/tree/feat/arch32

To compile it:

git clone -b feat/arch32 https://github.com/codenotary/immudb
GOOS=linux GOARCH=arm make immudb-static

After compiling immudb successfully, you can copy the binary to your Raspberry Pi and run it.

pi@raspberrypi:~ $ file immudb
immudb: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 3.2.0, Go BuildID=TxxkBVvt8FdwuoIF2tEm/OPsPR6svuMAkJjgMkcM-/fOv8jdEgvaxbsCClESmX/LMxHKjo4E-Ce3YMYMDZV, BuildID[sha1]=9c97b6a3ad64bb9691b126c3daf877555a105ec5, stripped
pi@raspberrypi:~ $ ./immudb
 _                               _ _
(_)                             | | |
 _ _ __ ___  _ __ ___  _   _  __| | |__
| | '_ ` _ | '_ ` _ | | | |/ _` | '_ 
| | | | | | | | | | | | |_| | (_| | |_) |
|_|_| |_| |_|_| |_| |_|__,_|__,_|_.__/

================ Config ================
Data dir        : ./data
Address         : 0.0.0.0:3322
Metrics address : 0.0.0.0:9497/metrics
Config file     : configs/immudb.toml
MTLS enabled    : false
Auth enabled    : true
Dev mode        : false
Default database: defaultdb
Maintenance mode: false
----------------------------------------
Superadmin default credentials
   Username     : immudb
   Password     : immudb
========================================

immudb  2020/10/01 15:23:33 INFO: Admin user immudb successfully created
immudb  2020/10/01 15:23:33 INFO: Started with an empty database
immudb  2020/10/01 15:23:33 INFO: Starting consistency-checker
You can now use immuadmin and immuclient CLIs to login with the immudb superadmin user and start using immudb.

Now you can connect and use immudb with our SDKs:

https://github.com/codenotary/immudb#using-immudb

immudb

BUILT ON THE FASTEST
IMMUTABLE LEDGER
TECHNOLOGY

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

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.