/**

I design databases schema-first — the data model is the foundation of every application, and getting it right early saves enormous pain later.

I've used three different ORMs against PostgreSQL (Drizzle, Prisma, SeaORM) and each taught me something different. Drizzle feels closest to writing real SQL, Prisma has the smoothest migration workflow, and SeaORM integrates beautifully with Rust's type system.

For Hurivuri I used Drizzle to model a full e-commerce schema — product variants with per-combination pricing, order lifecycle state machines, multi-tier RBAC, affiliate commission tracking, and bilingual content fields. For Typcraft it was SeaORM in Rust — credit billing ledger, template versioning, and organization-level multi-tenancy.

Moonly runs on Prisma with NFT collection metadata, staking mission configurations, raffle state management, and wallet linking with signature verification. Solang Playground also uses Prisma for compilation analytics and deployment tracking.

Type-safe database access is non-negotiable for me — catching a schema change at compile time is the whole point of using an ORM in the first place.

Good schema design is invisible when it works and painful when it doesn't — I'd rather spend the time upfront than fight the database later.

*/