backend-dev-guidelines

To structure a maintainable Node.js and Express microservice, enforce a layered architecture routing requests from Routes to Controllers, then Services, and finally Repositories. This separation ensures predictable, observable backend systems.

The best way to validate input in TypeScript backend microservices is integrating Zod for schema validation. This enforces strict data checking and pairs with Sentry error tracking to maintain robust, reliable system boundaries.

Yes, this backend development approach requires dependency injection. It mandates dependency injection alongside the BaseController pattern to decouple components, ensuring your Node.js microservices remain highly testable and maintainable.

To implement a repository pattern with Prisma in Express, encapsulate database interactions within dedicated repository classes. This abstracts data access away from your services, ensuring predictable data handling and strict architectural boundaries.

You should enforce strict architectural doctrines in TypeScript backend systems when starting a new microservice or refactoring an existing one. This prevents common pitfalls and ensures high code quality, reliability, and observability from the start.