backend-dev-guidelines

Standardize Node.js and Express backend architecture by enforcing a layered pattern: routes to controllers to services to repositories. Adopt the BaseController pattern for new controllers and apply layering rules to all new services to ensure maintainability and consistency across microservices.

The best way to structure Prisma repositories is to integrate them within the repository layer of your architecture. Centralize error handling using provided utilities, and enable startup validation of configuration to align your middleware, testing, and monitoring practices.

Yes, this backend development approach works with Zod and Sentry. It provides comprehensive workflows for error handling, performance monitoring, and migrations, specifically offering guidance on integrating Prisma, Sentry, Zod, and unifiedConfig within your microservices.

Apply a layered architecture workflow by creating new routes that direct traffic to controllers. Controllers should then delegate business logic to services, which interact with repositories. This reduces variability and enforces consistency across your Node.js and TypeScript backend.

You need centralized configuration validation in Node.js microservices when you want to prevent startup failures from invalid settings. Enabling startup validation of configuration using unifiedConfig ensures that your backend services fail fast if required environment variables or settings are missing.