database-design

Schema design for multi-tenant applications requires principled guidance on normalization, primary key strategies, and foreign keys to ensure scalable data models. This skill evaluates your entity relationships and indexing plans to reduce costly rework early in the architecture phase.

Choosing between PostgreSQL, Neon, Turso, and SQLite-like solutions depends on your specific deployment needs and architecture scale. This skill provides decision support to help you select the appropriate serverless database by evaluating your data modeling requirements and performance constraints.

Evaluating indexing strategies and normalization for performance tuning involves analyzing your schema structure, timestamp usage, and primary keys against established best practices. This skill guides decisions on indexing plans and normalization levels to optimize relational and serverless database performance.

Selecting the right ORM between Drizzle, Prisma, and Kysely depends on your schema design and serverless deployment context. This skill offers decision support for ORM choices, ensuring your selected tool aligns with your data modeling strategy and database architecture.

You need a schema migration plan for initial data modeling when creating new scalable data models or evaluating entity relationships for deployment. This skill applies to initial data modeling and schema migrations, guiding decisions on key fields, timestamps, and indexing strategies.