How dokkabei97/mvp works
High-Level Architecture Overview
a. Core Domains (5 main bounded contexts):
• Member
• Compare
• Pay
• Review
• Search
b. For each domain, represent the hexagonal architecture layers:
• Domain Layer (innermost)
• Application Layer (middle)
• Adapter Layer (outermost)
Detailed Component Breakdown
For each bounded context, show:
a. Domain Layer:
• Domain Models (e.g., Member, Gender in member-domain)
• Domain Logic
b. Application Layer:
• Use Cases (e.g., MemberReaderUseCase, MemberStoreUseCase)
• Ports
• Input Ports (e.g., MemberReaderUseCase)
• Output Ports (e.g., MemberReaderPort)
• Services (e.g., MemberService)
c. Adapter Layer:
• Input Adapters (Controllers)
• Output Adapters (Repositories)
• DTOs
• Infrastructure components
Shared Components
• Core module (shared/core)
• Common Response handling
• Utility classes
• Persistence module (shared/persistence)
Specific Implementation Details
For each bounded context (using Member as an example):
┌─────────────────────────────────────────────────┐
• Member Bounded Context │
• ┌─────────────┐ ┌─────────────┐ ┌─────────────┐│
• Domain │ │Application │ │ Adapters ││
• Member │ │- UseCase │ │- Controller ││
• Gender │ │- Ports │ │- Repository ││
• ┘ └─────────────┘ └─────────────┘│
• ┘
Technical Stack Indicators
Technology badges or labels for:
• Kotlin
• Spring Boot (implied by application structure)
• Gradle
• Exposed (SQL framework, seen in ExposedConfig)
• Showing the hexagonal architecture principles
• Representing DDD concepts
• Illustrating the MonoRepo structure
• Displaying technical implementation details
• The overall system structure
• How different bounded contexts interact
• The flow of data and dependencies
• The implementation of hexagonal architecture principles
• The relationship between different layers and components