backend-dev-guidelines

Layered backend architecture separates concerns by routing requests through Routes → Controllers → Services → Repositories → Database. This structure prevents cross-layer leakage, ensuring predictable and maintainable services.

Standardize validation and error handling in a TypeScript backend by centralizing configuration and using Zod schemas. Explicit error handling and unified configuration ensure reliable and robust service operations.

Enforce observability across microservices and monoliths by integrating Sentry for errors and performance monitoring. Strong testing discipline and robust error handling maintain quality and safety controls.

Yes, these backend development guidelines apply to both microservices and monoliths. They mandate consistent practices for routing, controllers, services, repositories, and configuration regardless of architectural scale.

Common anti-patterns in Express and TypeScript services include bypassing the Routes → Controllers → Services → Repositories hierarchy, mismanaging dependency injection, and lacking explicit error handling or unified configuration.