Bootstrapping uclosset-server: Building a Scalable Foundation with NestJS and Prisma

Initial Setup

Starting a new project requires balancing development speed with long-term maintainability. For the uclosset-server project, we have initiated the foundation using NestJS as our primary framework, leveraging its robust dependency injection and modular architecture to ensure the codebase remains clean as it grows.

The Architecture

To interact with our data layer, we integrated Prisma as our ORM. By centralizing database operations through a repository-like pattern, we can decouple our business logic from specific database queries, making the application easier to test and modify.

// Example of a centralized data repository
@Injectable()
export class UserProfileRepository {
  constructor(private readonly prisma: PrismaService) {}

  async findById(id: string) {
    return this.prisma.user.findUnique({
      where: { id },
    });
  }
}

Data Layer Design

Our schema design follows normalized principles to ensure relational integrity within PostgreSQL. By defining clear relationships, we can easily scale features without introducing inconsistent data.

-- Schema definition for core data
CREATE TABLE app_config (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  settings JSONB NOT NULL,
  updated_at TIMESTAMP WITH TIME ZONE DEFAULT CURRENT_TIMESTAMP
);

Key Decisions

1. Modular Architecture - Utilizing NestJS modules allows us to isolate domains effectively.
2. Type Safety - By using TypeScript alongside Prisma, we get end-to-end type safety from the database schema to the API layer.
3. Automated Quality Control - Integrating ESLint and Prettier ensures consistent code formatting and identifies potential issues before they hit the repository.

Lessons Learned

Setting up a project correctly from version 0.0.1 is critical. By investing time in establishing linting, type safety, and a solid DI structure early, we reduce technical debt that typically plagues rapid prototyping.

Takeaway

Start your next backend project by defining your data relationships clearly in Prisma before building out your service layer; this prevents major refactors later in the development cycle.

Generated with Gitvlg.com