backend-dev-guidelines

Structure a Node.js Express backend using a layered architecture that separates concerns across routes, controllers, services, and repositories. This approach enforces consistency and maintainability across microservices by isolating business logic from data access and request handling.

The best way to validate API request data in Express microservices is using Zod. It provides schema validation directly within your TypeScript request lifecycle, ensuring incoming data matches expected types before reaching controller or service layers.

Error tracking with Sentry in a TypeScript backend works by capturing unhandled exceptions across the request lifecycle. Integrating Sentry middleware ensures runtime errors in controllers or services are automatically reported for debugging.

Yes, you can use a layered architecture for small Node.js microservices. Separating routes, controllers, services, and repositories establishes consistent patterns that scale effectively and simplify future feature additions without creating structural overhead.

Manage configuration across multiple Node.js microservices using a unified configuration approach like unifiedConfig. This standardizes environment variables and application settings, maintaining consistency and preventing configuration drift across different services.