database-design

Design a database schema by defining entities, relationships, primary keys, and timestamp conventions, then applying normalization principles to model data correctly. Provide your domain model and expected query patterns to generate a maintainable schema structure.

Choosing a database for serverless or edge deployments requires evaluating latency needs, feature sets like vector search, and connectivity constraints rather than defaulting to a traditional hosted option. Match the database selection to your specific environment requirements.

Choose the right indexes by analyzing expected query patterns and applying an indexing strategy that prevents N+1 queries and full table scans. Use EXPLAIN ANALYZE to validate query performance and avoid anti-patterns like SELECT * in production workloads.

Plan safe database migrations by defining incremental migration steps that preserve existing data and avoid breaking changes. Structure referential actions like ON DELETE behavior carefully to maintain referential integrity throughout the refactoring process.

Select an ORM by matching its capabilities to your database choice, schema design requirements, and specific deployment scenario like serverless or edge. Consider how the ORM handles relationship modeling, migrations, and query optimization to ensure compatibility.