backend-dev-guidelines

To structure a scalable Node.js backend, enforce a layered architecture routing from Routes to Controllers, Services, and Repositories. This separation isolates non-HTTP business logic and standardizes patterns using BaseController and dependency injection.

Standardizing Node.js microservices architecture involves enforcing strict directory naming conventions, mandatory SKILL.md documentation, and unified configuration. This ensures consistent observability with Sentry and reduces onboarding friction across backend teams.

Implement data validation and database access by integrating Zod for request validation and Prisma for repository patterns. This enforces type safety and abstracts database operations within the Services layer of your Node.js backend.

Yes, this backend architecture standard requires Sentry integration for observability and Zod for validation. It also mandates Prisma repositories, async error handling, and a unifiedConfig setup to maintain quality in Express TypeScript projects.

You need a BaseController and dependency injection to separate non-HTTP business logic from Express routes. This pattern enforces a standardized layered architecture, making your Node.js microservices less brittle and easier to maintain.

Node.js Express microservices should follow testing discipline strategies and integrate Sentry for error observability. These standards are enforced alongside async error handling to ensure reliability across your TypeScript backend services.