How almeydajuan/monorepo-poc works
Main Components Identification
The project is a monorepo containing several distinct components:
a. Core Applications:
• TicTacToe4k (a game service)
• User Service (user management)
b. Utility Modules:
• approve-script
• database-script
• metadata-generator
• infra (shared infrastructure)
┌─ Applications Layer ─────────────────────┐
• ┌─ TicTacToe4k ─┐ ┌─ User Service ─┐│
• Frontend │ │ Backend API ││
• Backend │ │ Domain Logic ││
• Domain Logic │ │ Repositories ││
• ┘ └────────────────┘ │
• ┘
┌─ Shared Infrastructure ─────────────────┐
• ┌─ Database ─┐ ┌─ Infrastructure ──┐ │
• Postgres │ │ Storage │ │
• Migrations │ │ Database Env │ │
• ┘ └──────────────────┘ │
• ┘
┌─ Build & Development Tools ────────────┐
• ┌─ Scripts ──┐ ┌─ Metadata Gen ──┐ │
• Approve │ │ YAML Config │ │
• Database │ │ Pipeline Config │ │
• ┘ └────────────────┘ │
• ┘
Component Relationships
• Service dependencies on shared infrastructure
• Database connections (especially for User Service)
• Build tool relationships with applications
Important Details
a. Technology Stack Indicators:
• Kotlin as primary language
• Http4k for web services
• Gradle for build system
• PostgreSQL for database
b. Key Architectural Patterns:
• Repository pattern (visible in user/repository)
• Clean Architecture (domain, backend separation)
• Hexagonal Architecture (ports and adapters in database-script)
Specific Implementation Notes
Annotations showing:
• Docker compose configurations for databases
• Test fixtures and testing strategy
• Metadata generation flow
• CI/CD pipeline integration (.github/workflows)