database-design

Schema design for scalable systems requires applying a decision checklist to clarify requirements, ensuring normalized schemas, proper primary keys, appropriate timestamps, and robust indexing across serverless or traditional deployments.

Database design anti-patterns to avoid include over-indexing, using SELECT * in production queries, ignoring schema normalization, and defaulting to a single database choice like PostgreSQL for every context without evaluating requirements.

ORM and database selection for serverless deployments requires context-driven decisions using a before-design checklist to evaluate schema relationships and environment constraints, rather than defaulting to traditional databases like PostgreSQL for every project.

Planning indexing strategies requires a guidance framework that enforces robust indexing while avoiding over-indexing, ensuring indexes match your query patterns and maintain normalized schemas for production systems.

Avoid defaulting to PostgreSQL when your project context, serverless deployment constraints, or specific data relationships indicate alternative database technologies would better serve your schema design and scaling requirements.