How gabrielmatsan/fast-feet works
Project type and purpose
• This is a backend‐only, full-stack server application built with NestJS using a Domain-Driven Design (DDD) / Hexagonal (Onion) architecture.
• Purpose: Manage a delivery system (orders, delivery persons, recipients, attachments) and an associated notification system (push notifications on "order delivered/in-transit/returned").
File structure
• Top-level “src” folder contains:
• core – generic building blocks (Either, Entities, ValueObjects, DomainEvents).
• domain – two bounded contexts: delivery and notification; each has:
‑ enterprise/entities (rich domain model)
‑ application/use-cases (business logic)
‑ application/repositories (ports/interfaces)
‑ (delivery only) criptography, storage, events
• infra – adapters/drivers:
‑ http/controllers (NestJS REST API)
‑ database/prisma (ORM mappers & repository implementations)
‑ auth (JWT guards/strategies, decorators)
‑ events (NestJS event-bus subscribers & e2e tests)
‑ storage (R2/S3 uploader)
‑ env (configuration)
‑ main.ts & AppModule (composition root)
• Prisma folder holds DB schema, migrations, and generates TypeScript client.
• docker-compose.yml likely spins up Postgres (or other) plus S3 emulator.
README
• Confirms a NestJS server app starter: “building efficient and scalable server-side applications.”
Elements
• “Controllers” (HTTP Layer)
• “Use-Cases” (Application Layer)
• “Entities & Domain Events” (Domain Layer)
• “Repositories” (Interfaces) & “Prisma Repositories” (Infra)
• “Storage Adapter”, “Cryptography Adapter”, “Event Bus”
• “PostgreSQL” and “Cloud Storage” as external systems
• Request/response flow
• Domain event emission & subscription
• Adapter calls to external systems
• Blue for core/domain elements
• Green for application/use-cases
• Orange for infra/adapters
• Grey for external services