How ankalago/multiplo-test works
Main Components Identification
The system should be represented as two main sections:
Frontend (React Application):
• Present as a layered architecture with:
• Presentation Layer (Components)
• State Management Layer (Redux)
• Services Layer
• Utils/Hooks Layer
Backend (Hexagonal Architecture):
• Core hexagon containing:
• Application Layer (Use Cases)
• Domain Layer
• Ports (Interfaces)
• Adapters Ring containing:
• Controllers
• Repositories
• Infrastructure components
┌─ Frontend Container ──────────────────────┐
• ┌─ Components ─────┐ ┌─ Store ────────┐ │
• Pages │ │ - Redux Store │ │
• Layout │ │ - State Slices │ │
• UI Components │ └────────────────┘ │
• ┘ │
• ┌─ Services ──────┐ ┌─ Utils/Hooks ──┐ │
• API Services │ │ - Custom Hooks │ │
• Axios Config │ │ - Utilities │ │
• ┘ └────────────────┘ │
• ┘
┌─ Backend Hexagon ──────────────────────────┐
• ┌─ Application Core ─────────────────┐ │
• ┌─ Domain ─────┐ ┌─ Use Cases ──┐ │ │
• Post Entity│ │ - Create Post │ │ │
• Interfaces │ │ - Get Posts │ │ │
• ┘ │ - Update Post │ │ │
• ┘ │ │
• ┘ │
• ┌─ Adapters ──────────────────────────┐ │
• Controllers │ │
• Repositories │ │
• ┘
• ┌─ Infrastructure ───────────────────┐ │
• Prisma DB │ │
• SQLite Database │ │
• ┘
• ┘
Connection and Data Flow
• Frontend-Backend communication via REST API
• Internal frontend data flow (Components → Redux → Services)
• Internal backend flow (Controller → Use Cases → Repository → Database)
Additional Elements
Include:
• API endpoints (/api/v1/post)
• Testing coverage indicators
• External services (Vercel, Railway)
• Database schema representation