How eliran-turgeman/collecto works
Main Components Identification
a. Frontend Layer:
• Web UI (Pages directory with Razor Pages)
• Identity Management UI (Areas/Identity)
• Swagger UI for API documentation
b. Backend Layer:
• API Controllers
• Services Layer
• Repository Layer
• Domain Layer
• Authentication/Authorization
• Email Processing
• Export Services
c. Data Layer:
• Database (Entity Framework Core with migrations)
• File System Storage (for templates)
d. External Services:
• SMTP Server Integration
• Payment Processing (LemonSqueezy)
• reCAPTCHA Integration
┌─────────────────────────────────────────────────────┐
• Client Layer │
• (Web UI, API Consumers, Swagger UI) │
• ┤
• API Layer │
• (Controllers, Authentication, CORS, Middleware) │
• ┤
• Service Layer │
• (Email, Forms, Templates, Exports, Validations) │
• ┤
• Repository Layer │
• (Data Access, Entity Framework Core) │
• ┤
• Data Layer │
• (Database, File System) │
• ┘
Component Relationships
a. Data Flow:
• Client → API (REST calls)
• API → Services (Business logic)
• Services → Repositories (Data access)
• Repositories → Database (CRUD operations)
b. External Interactions:
• Email Service → SMTP Server
• Payment Service → LemonSqueezy
• Validation Service → reCAPTCHA
Key Features to Highlight
Specialized components for:
• Email Template Management
• Export Functionality (CSV/JSON)
• Custom Email Validation
• API Key Authentication
• CORS Management
• User Management
Specific Implementation Details
Important architectural patterns:
• Repository Pattern implementation
• Service Layer abstraction
• Feature Toggle system
• Export Strategy Pattern
• Template Storage Provider abstraction