backend-dev-guidelines

Structure a scalable Node.js backend by separating routes, controllers, services, and repositories. This playbook codifies that layered architecture pattern using a BaseController to standardize request handling and enforce separation of concerns across microservices.

Standardize backend configuration and error handling by centralizing them with a unifiedConfig pattern and Sentry integration. This ensures consistent observability and configuration management across all microservices in your stack.

Apply dependency injection in a TypeScript Express backend to decouple service creation from route controllers. The guidelines prescribe specific DI patterns that maintain consistent architecture and simplify testing across your services.

Yes, you can migrate a legacy Express and Prisma application using the included migration guidance. It provides structured examples for transitioning legacy patterns to modern Node.js, Express, and TypeScript stacks.

You need Zod validation in a backend service architecture to enforce runtime type safety for incoming requests. The guidelines prescribe Zod usage alongside controllers to ensure data integrity before processing business logic.

Use testing strategies that target the isolated layers of your Node.js microservices. The playbook centralizes testing approaches for routes, controllers, services, and repositories to ensure reliable validation across the layered architecture.