backend-dev-guidelines

Structure a scalable Node.js Express backend using layered architecture: routes delegate to controllers, controllers handle HTTP concerns, services contain business logic, and repositories manage data access. This separation enforces clear responsibilities and testability across microservices.

Standardize Express API responses using a BaseController pattern that enforces consistent HTTP response structures and integrates centralized error handling with Sentry for performance monitoring and automated exception tracking across all endpoints.

Validate input using Zod schemas and manage type-safe configuration through a unifiedConfig utility. This enforces runtime type checking and environment variable validation, preventing invalid data from entering your Node.js backend services.

Yes, the architecture pattern supports Prisma ORM for data access by standardizing repository implementations. Prisma queries are encapsulated within the repository layer, keeping database logic isolated from business services and ensuring consistent data access patterns.

Yes, you can migrate legacy Node.js codebases to these structured patterns using the provided migration guidance. It helps refactor existing codebases into modern, testable structures with dependency injection, layered architecture, and standardized testing strategies.

Layered Node.js Express architectures enable isolated unit testing of services, controllers, and repositories using dependency injection. This separation allows mocking data access and business logic independently, ensuring comprehensive test coverage without external dependencies.