backend-dev-guidelines

Standardize tRPC router setup by delegating entry points to a service layer and using repositories for complex Prisma queries. Validate inputs with Zod and enforce projectId tenant filtering for strict data isolation.

The best way to enforce multi-tenant isolation is by applying projectId filtering across all data access layers. This ensures queries in Prisma and ClickHouse are scoped to the correct tenant throughout the service layer.

Validate backend environment variables and inputs by using env.mjs for configuration and Zod for schema validation. This enforces type safety and prevents invalid data from entering tRPC procedures or public API endpoints.

Yes, you can use ClickHouse alongside Prisma for queue processors. The guidelines standardize data access patterns for both tools within BullMQ workers, ensuring proper OpenTelemetry instrumentation and separation of data layers.

OpenTelemetry instrumentation for BullMQ queue processors works by tracing background jobs across the service layer. It standardizes observability for queue processing, linking telemetry spans to specific tasks and multi-tenant data access operations.

Testing strategies for tRPC procedures and public API routes should cover entry, service, and data layers. The guidelines provide robust testing patterns that validate Zod schemas, projectId tenant filtering, and ClickHouse query logic.