backend-dev-guidelines

To enforce layered architecture in Node.js, apply standards mandating a Routes → Controllers → Services → Repositories flow. This separates concerns and standardizes configuration via a unified config, ensuring predictable, observable backend systems.

The best way to validate input and track errors in TypeScript backend services is enforcing Zod for validation and Sentry for error tracking. This provides strict runtime type checking and automated exception capture.

Implementing a BaseController pattern with dependency injection in TypeScript standardizes request handling and decouples business logic. This ensures maintainable backend systems by routing logic through reusable, testable components.

Yes, you can use Prisma repositories with Express microservices. Enforcing Prisma repositories standardizes database access within the repository layer, ensuring data operations are predictable and maintainable across Node.js applications.

You need architectural enforcement for backend development when creating a new microservice or refactoring an existing one. It acts as a comprehensive checklist to ensure code adheres to production-ready standards from design to deployment.