backend-developer

Backend CRUD with Drizzle ORM in Next.js uses server actions and a many-first design pattern: always operate on arrays for bulk mutations. Create server actions in `src/actions/` with the 'use server' directive, define model operations via `createModelFactory` from `src/lib/models/`, and use Drizzle's typed queries for type-safe database access. This enforces reliable, transaction-safe batch processing.

Server actions are preferred over API routes for backend mutations in Next.js because they simplify data access, improve reliability, and integrate directly with TypeScript. They eliminate the need for client-server serialization overhead and provide built-in Zod-based validation alongside Drizzle ORM integration for safer, more maintainable backend logic.

The many-first design pattern enforces batch operations on arrays rather than single records. Use Drizzle's bulk insert, update, and delete methods within server actions to process multiple rows atomically. Wrap operations in transactions to ensure data consistency, and validate array inputs with Zod before executing mutations.

The model factory pattern centralizes all data access logic for a domain model into a single factory function. It simplifies tests by providing a mockable interface, reduces code duplication across server actions, and enforces consistent Drizzle ORM query patterns. Export factories from `src/lib/models/` for use across your application.

Define your database schema using Drizzle's TypeScript API in `src/lib/models/`, then run migrations via the Makefile target. Drizzle generates migration files automatically, and you execute them to keep your database in sync. This typed approach catches schema mismatches at development time and ensures consistency across environments.

Yes. Drizzle ORM works seamlessly with server actions while avoiding dynamic imports—a tested, typed pattern in this Skill. Define model factories as static exports, import them directly in server actions, and leverage TypeScript's static analysis. This maintains LSP tooling support and ensures your backend logic is fully type-checked at build time.