backend-dev-guidelines

Structure tRPC routers and services in a TypeScript monorepo using a layered architecture: tRPC/API routes delegate to services, which call repositories for database access via Prisma or ClickHouse, ensuring clear separation of concerns and maintainability.

The best way to validate API requests in a tRPC backend is using Zod validation schemas within your procedure definitions to enforce data integrity before passing requests to the underlying service layer.

Implement BullMQ queue processors in a Next.js 14 backend by following standardized backend guidelines that define how to structure processor files, delegate tasks to services, and integrate observability tools like OpenTelemetry for job tracing.

Yes, this backend architecture supports observability with OpenTelemetry and DataDog by providing consistent patterns for integrating tracing and monitoring across tRPC routers, public API endpoints, and queue processors.

Use Jest and Vitest testing strategies for a TypeScript monorepo backend by writing tests that validate tRPC procedure definitions, service layer logic, and repository interactions with PostgreSQL and ClickHouse databases.

Access PostgreSQL and ClickHouse databases in a layered backend architecture through repository components that handle database interactions, receiving data requests from the service layer to maintain separation from business logic.