backend-patterns

Standardize backend architecture patterns by adopting unified tools like oRPC for contracts, Drizzle ORM for data access, and Valkey for caching. This approach ensures consistent API design, reliable transactions, and centralized observability across all services.

Structure oRPC contracts and Drizzle ORM by defining type-safe procedures and routers with oRPC, then using Drizzle with Postgres for predictable data access and migrations. This combination ensures interoperability and reliable database transactions across the stack.

Valkey caching works with Better Auth by using Redis-backed Valkey for fast session lookups and authentication state. Better Auth manages the session lifecycle while Valkey provides the high-speed caching layer to reduce database load during authentication checks.

You can use Inngest for background processing and Pino for structured logging together within a unified backend pattern. Inngest handles asynchronous workloads while Pino captures centralized, structured observability data across the distributed services.

Rate-limiter-flexible integrates with Redis to protect API routes by applying rate limits and standardized error handling. It leverages the Redis-backed infrastructure to track request counts and prevent abuse across distributed backend services.