Add Immudb as a Dapr state store component

[rzamoramx]

New Dapr state store component

Hi all, I propose adding Immudb as a new state store component for Dapr. Here are some highlights about Immudb:

• Open Source and written in Go
• Immutable and cryptographically secure
• Operates as a key-value or SQL database
• Can run as a full database server with replicas or be embedded
• High performance (creator claims millions of writes per second)
• Auditable

Some use Cases:

• Financial applications
• Lightweight ledgers
• Event sourcing pattern (event log)

Implementation Details

• Client SDK: I am using the official Immudb SDK (github.com/codenotary/immudb/pkg/client).
• Supported Operations: For now, only basic CRUD operations are supported.
• Data Model: as a key-value database.
• Deployment Mode: as a full server.

Considerations

• Compatibility: Immudb uses its own gRPC API, so it does not align with protocols used by existing Dapr components.
• Scalability: Immudb is not distributed; scaling is vertical only.
• Client side: Immudb generates .state-* and .identity-* files on the client side, which are needed to establish trust with the server.

Documentation

• https://immudb.io/oss-new
• https://docs.immudb.io/1.9.5/immudb.html#what-is-immudb
• https://arriqaaq.medium.com/deep-dive-into-the-internals-of-an-immutable-database-immudb-3bdf9a0c2faa
• https://codenotary.s3.amazonaws.com/Research-Paper-immudb-CodeNotary_v3.0.pdf