backend-dev-guidelines

Structure a new tRPC router by routing entry points through a service layer to repositories and databases. This enforces layered architecture across web and worker packages, standardizing backend patterns for Next.js and Express.

Isolate tenant data by applying projectId filtering across all database integrations. This dual PostgreSQL and ClickHouse strategy ensures strict tenant isolation and secure data access for backend services.

Handle backend errors and observability by implementing traceException error handling and OpenTelemetry instrumentation. This centralized approach standardizes error tracking across tRPC procedures and BullMQ workers.

The guide includes input validation and testing conventions for BullMQ workers. It enforces Zod validation and specifies vitest for worker testing, while utilizing Jest for web package testing.

You can use this guide for creating public API routes alongside tRPC procedures. It provides standardized architectural patterns for both entry points, ensuring consistent env configuration and observability.