How dmalykh/taxonomy works
Main Components Identification
a) API Layer (Multiple Interfaces):
• GraphQL API Server
• gRPC API Server
• CLI Interface
b) Core Service Layer:
• Namespace Service
• Term Service
• Vocabulary Service
• Reference Service
c) Repository Layer:
• EntGo Database Abstraction
• Database (configurable through DSN)
Architectural Pattern Representation
┌─ API Layer ─────────┐
• GraphQL │
• gRPC │
• CLI │
• ┬────────────┘
┌────────▼────────────┐
• Service Layer │
• Namespace │
• Term │
• Vocabulary │
• Reference │
• ┬────────────┘
┌────────▼────────────┐
• Repository Layer │
• EntGo │
• ┬────────────┘
┌────────▼────────────┐
• Database │
• ┘
Specific Elements
• Blue: API interfaces
• Green: Core services
• Yellow: Repository layer
• Gray: Database layer
b) Component Relationships:
• Data flow directions
• Dependency injection points
Important Details to Highlight
a) API Layer:
• GraphQL schema structure (from /src/api/graphql/schema/)
• gRPC service definitions (from /src/api/grpc/proto/)
• CLI commands structure (from /src/cmd/)
b) Domain Model:
• Term
• Vocabulary
• Namespace
• Reference
• Entity relationships
c) Repository Pattern:
• EntGo implementation
• Database agnostic design
Key Relationships to Emphasize
• Term-Vocabulary relationships (unique constraints)
• Namespace-Entity relationships
• Reference management system
• Service-Repository interaction patterns
This approach will provide a clear understanding of both the high-level architecture and the detailed implementation structure while maintaining the clean architecture principles evident in the codebase.