backend-dev-guidelines

Layered architecture in backend microservices separates concerns into routes, controllers, services, and repositories. This structure ensures maintainable Node.js and Express applications by isolating business logic from data access and routing layers.

You validate request data in Node.js and Express using Zod by defining schema validation rules within your controller patterns. This enforces consistent backend practices and prevents invalid data from reaching your service or repository layers.

The best way to structure a TypeScript backend API endpoint is following the repository pattern and using a BaseController. This enforces consistent code practices across microservices, standardizing routing, service logic, and data access implementation.

You integrate Sentry error tracking into a Node.js and Express microservice as part of your core backend development rules. This ensures robust error monitoring and consistent configuration management across all your distributed services.

This backend microservice guide includes configuration management as a core best practice. You establish consistent configuration handling across Node.js and Express services to ensure maintainable and scalable distributed architectures.

You need the repository pattern for backend microservices when establishing a clean separation of concerns between your data access and business logic. It ensures maintainable TypeScript service layers by abstracting database interactions.