backend-dev-guidelines

Structure backend features in a Next.js and tRPC monorepo by enforcing a layered architecture with thin entry points, service orchestration, and data access repositories to ensure separation of concerns and maintainability.

The best way to implement tenant isolation for multi-tenant backend APIs is to enforce projectId tenant isolation throughout your service and repository layers, ensuring data access is strictly scoped per project.

Validate inputs and manage configuration in a tRPC router by using Zod v4 for schema validation and loading environment variables through env.mjs and env.ts files for centralized config management.

Add observability to BullMQ queue processors and tRPC procedures by integrating OpenTelemetry, which provides structured tracing and monitoring across your web and worker packages.

Yes, this backend layering guide supports both Prisma and ClickHouse data access by providing structured checklists for repositories, ensuring consistent data flow patterns across relational and analytical databases.

You should separate service logic from data access repositories in backend development when building scalable features, allowing services to orchestrate repository calls while keeping database queries isolated and maintainable.