How dimo-network/identity-api works
Main Components
a. API Layer
• GraphQL API Server (evident from /graph directory)
• Schema Definitions (found in /graph/schema/*.graphqls)
• Resolvers (various *.resolvers.go files)
b. Core Services Layer
• Contract Event Services (/internal/services)
• Staking Services (/internal/services/staking)
• Tableland API Service
• Data Loaders (/internal/loader)
c. Repository Layer
• Vehicle Repository
• Aftermarket Repository
• DCN Repository
• Manufacturer Repository
• Stake Repository
• Synthetic Device Repository
• Developer License Repository
• Privileges Repository
d. Database Layer
• PostgreSQL Database (evident from migrations and sqlboiler.toml)
e. External Integrations
• Blockchain Contracts (from /internal/contracts)
• Tableland Integration
Component Relationships
• Client Requests → GraphQL API
• GraphQL API → Data Loaders → Repositories
• Repositories → PostgreSQL Database
• Contract Events Consumer → Blockchain
• Services → Tableland API
• Services → Repositories
Architectural Patterns to Highlight
• GraphQL-first architecture
• Repository pattern implementation
• Event-driven architecture for blockchain events
• Data loader pattern for N+1 query prevention
[Client Layer]
• ↓
[GraphQL API Layer]
• ↓
[Data Loader Layer]
• ↓
[Services Layer]
• ↓
[Repository Layer]
• ↓
[Database Layer]
[External Systems]
• Blockchain ←→ Contract Events Consumer
• Tableland API ←→ Services Layer
Important Details to Include:
Configuration Management
• Settings.yaml configuration flow
• Environment variables handling
Infrastructure Components
• Kubernetes deployment elements (from /charts directory)
• Monitoring setup (ServiceMonitor)
Data Flow Patterns
• Vehicle-centric data model
• Privilege and access control flows
• Device pairing relationships
This architecture represents a modern GraphQL API system with blockchain integration, following clean architecture principles with clear separation of concerns between layers.