backend-dev-guidelines

Structure Express microservices by enforcing layered separation with distinct routes, controllers, services, and repositories. This approach moves business logic out of routes, preserves testability, and maintains clean architectural boundaries across growing Node.js codebases.

Validate input in Node.js backend services using Zod validation flows. This enforces consistent, production-grade data validation for routes and controllers, preventing brittle implementations and ensuring safe data processing.

Prisma repository-based data access isolates database operations within a dedicated repository layer. This enforces strict separation from services and controllers, preserving testability and maintaining clean architectural boundaries in TypeScript microservices.

Yes, you can use Sentry for error monitoring and observability in Express microservices. Implementing Sentry capture enforces production-grade error-handling standards and centralized configuration across your Node.js backend architecture.

You need dependency injection in Node.js TypeScript backend systems when enforcing production-grade architecture. It preserves testability, maintains clean boundaries, and ensures strict layered separation across controllers, services, and repositories.