How bursuc31/nestjs-task-svc works
Main System Components
a) API Layer
• NestJS application as the main container
• Two main modules: Auth Module and Tasks Module
• Controllers (auth.controller.ts and tasks.controller.ts) as entry points
b) Service Layer
• AuthService and TasksService as business logic handlers
• JWT Strategy implementation for authentication
• Custom guards and decorators
c) Data Layer
• Repositories (UserRepository and TaskRepository)
• Entity definitions (User and Task entities)
• TypeORM configuration
d) Infrastructure
• Docker container
• AWS Elastic Beanstalk deployment
• Database connection (likely PostgreSQL based on TypeORM usage)
Component Relationships
• Client requests → Controllers
• Controllers → Services
• Services → Repositories
• Repositories → Database
• Auth flow through JWT Strategy
Specific Implementation Details
• Blue rectangles for Controllers
• Green rectangles for Services
• Yellow diamonds for DTOs
• Purple rectangles for Entities
• Red hexagons for Guards/Middleware
Architectural Patterns
Following patterns:
• Module-based architecture (NestJS standard)
• Repository pattern for data access
• DTO pattern for data transfer
• Guard pattern for authentication
• Dependency injection system
[Client Layer]
• ↓
[API Layer (Controllers)]
• ↓
[Auth Guard/Middleware]
• ↓
[Service Layer]
• ↓
[Repository Layer]
• ↓
[Database Layer]
Additional Elements
• Configuration management (config folder structure)
• Environment-specific settings
• Testing setup (E2E and unit tests)
• Docker containerization flow
• AWS deployment pipeline
Technical Stack Indicators
• NestJS framework
• TypeScript
• TypeORM
• JWT authentication
• Docker
• AWS Elastic Beanstalk
• PostgreSQL