backend-dev-guidelines

To structure a tRPC router in a Next.js 14 monorepo, follow the backend development guidelines which enforce a layered architecture, tenant isolation, and specific validation patterns using Zod for maintainable backend services.

The best way to implement BullMQ queue processors is by consulting the backend guidelines, which outline the required patterns, architectural conventions, and testing strategies for background job processing within the ElasticDash monorepo.

To set up dual database access using Prisma and ClickHouse, apply the monorepo development best practices that dictate how to properly structure data access layers and manage dual database usage for PostgreSQL and ClickHouse.

Yes, the backend development approach supports OpenTelemetry observability. The guidelines explicitly cover how to integrate OpenTelemetry to ensure backend services maintain robust tracing and monitoring standards.

You need Zod validation for public API endpoints to ensure robust input checking. The backend guidelines specify the exact patterns and required checklists for implementing validation when exposing public API endpoints.

The recommended testing strategies for tRPC and Express services involve using Jest and Vitest. The backend guidelines provide comprehensive checklists to ensure these testing tools are correctly applied for maintainable backend code.