affinidi-did-resolver-cache-sdk

SDK for resolving Decentralised Identifiers (DIDs) with built-in local caching. Operates in local mode (resolving happens in your process) or network mode (requests are forwarded to a remote cache server).

Installation

[dependencies]
affinidi-did-resolver-cache-sdk = "0.8"

Supported DID Methods

Feature Flags

Usage

Local Mode (default)

use affinidi_did_resolver_cache_sdk::{config::ClientConfigBuilder, DIDCacheClient};

let config = ClientConfigBuilder::default().build();
let resolver = DIDCacheClient::new(config).await?;

match resolver.resolve("did:key:z6Mkr...").await {
    Ok(result) => println!("Document: {:#?}", result.doc),
    Err(e) => println!("Error: {:?}", e),
}

Network Mode

Enable the network feature, then point to a running cache server:

let config = ClientConfigBuilder::default()
    .with_network_mode("ws://127.0.0.1:8080/did/v1/ws")
    .with_cache_ttl(60)            // Cache TTL in seconds
    .with_network_timeout(20_000)  // Timeout in milliseconds
    .build();
let resolver = DIDCacheClient::new(config).await?;

Network mode still caches locally to reduce remote calls.

Caching Strategy

The cache uses per-method TTL to avoid unnecessary re-resolution:

The cache_ttl configuration option only applies to mutable DID methods. Immutable DIDs stay cached until evicted by capacity pressure, since their documents can never change.

Benchmarks

cargo run --features network --example benchmark -- \
  -g 1000 -r 10000 -n ws://127.0.0.1:8080/did/v1/ws

Running Tests

Integration tests require the network feature:

cargo test --features network

Related Crates

• affinidi-did-resolver-cache-server — Remote cache server
• affinidi-did-common — DID Document types (dependency)
• affinidi-did-resolver-traits — Pluggable resolver traits (dependency)

License

Apache-2.0