How affinidi/affinidi-did-resolver works
Key Components to Include:
Core Architecture Components
• DID Resolver Cache SDK
• DID Resolver Cache Server
• DID Resolver Methods
• External DID Networks/Services
Main System Relationships
A. SDK Layer:
• Networking module (request handling)
• Document caching system
• Resolver interface
• Configuration management
• Error handling system
B. Server Layer:
• HTTP and WebSocket handlers
• Session management
• Statistics collection
• Cache configuration
• Server core functionality
C. Methods Layer:
• DID method implementations (e.g., did-peer)
• Method-specific resolvers
• Custom implementations
• [Client Applications]
• ↓
• [SDK Layer (Local Cache)]
• ↓
• [Server Layer (Remote Cache)]
• ↓
• [DID Methods Layer]
• ↓
• [External DID Networks]
Component Relationships
• Bidirectional communication where applicable
Specific Elements
a. SDK Components:
• [Configuration Manager] → [Resolver Interface]
• ↓
• [Document Cache] ← → [Networking Module]
• ↓
• [Request Queue] → [Error Handler]
b. Server Components:
• [HTTP Handler] → [Session Manager]
• [WebSocket Handler] → [Cache Controller]
• ↓
• [Statistics Collector] ← [Server Core]
c. Method Implementation:
• [Method Registry]
• ↓
• [Individual Method Implementations]
• ↓
• [External DID Networks]
Additional Details
• Configuration nodes showing TOML file inputs
• Error handling paths
• Cache invalidation flows
• Scaling points
• Security boundaries
Integration Points
• Client application entry points
• External service connections
• Plugin/extension points
Remember to:
• Keep the main flow clear and centered
• Related components visually
• Notes for important configuration options
• Version compatibility where relevant
• Security boundaries and authentication points