How losefor/nest-starter works
Project Type and Purpose
• This is a production-grade Nest.js backend (modular monolith) with the following capabilities:
• REST API with versioning support
• Authentication (JWT + Passport) and ACL (CASL)
• File upload & image processing (Sharp)
• Database access via Prisma ORM (PostgreSQL/MySQL)
• Internationalization (i18n)
• A shared image-manipulation library under libs/
Main Architectural Layers & Components
• API Layer (Express + Nest Controllers)
• Routes grouped by modules: Auth, Users, Permissions, Uploads
• Business Logic Layer (Nest Services + CASL Ability Factory)
• Data Access Layer (Prisma Module & Services)
• Shared Library (Image-Manipulation Lib)
• Cross-cutting Modules & Middleware
• Common module (logging, version headers, user decorator)
• i18n module (localization JSON files)
• Guards & Strategies (JWT, permissions, anonymous)
• External Dependencies
• Relational Database (PostgreSQL/MySQL)
• Object Storage (DigitalOcean Spaces via Multer + Sharp)
• Process Management (PM2)
Relationships & Data Flow
1. Client → API Gateway (Nest + Express + Cors + Helmet + Morgan)
2. Controller (e.g., UploadsController) receives HTTP request
3. Guards & Interceptors enforce auth, permissions, versioning, i18n
4. Controller calls Service (e.g., UploadsService)
5. Service applies business rules, calls CASL Ability Factory if needed
6. For DB operations → PrismaService → Database
7. For file handling → Multer middleware → UploadsService → Sharp/Image-Manipulation Lib → DigitalOcean Spaces
8. Responses propagate back up to Controller and are sent to Client
Architectural Patterns & Principles
• Modular structure: each feature in its own Nest module
• Layered architecture: Controllers → Services → Prisma → DB
• Dependency Injection for services, Prisma client, and shared libs
• Separation of concerns: Auth, ACL, i18n, image processing all isolated
• Versioning enforced via custom decorators & interceptors
• Shared library (libs/image-manipulation) for reusable image logic