database-design
Data, Backend & APIDatabase design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
Documentation
Database Design
> Learn to THINK, not copy SQL patterns.
🎯 Selective Reading Rule
Read ONLY files relevant to the request! Check the content map, find what you need.
| File | Description | When to Read |
|------|-------------|--------------|
| database-selection.md | PostgreSQL vs Neon vs Turso vs SQLite | Choosing database |
| orm-selection.md | Drizzle vs Prisma vs Kysely | Choosing ORM |
| schema-design.md | Normalization, PKs, relationships | Designing schema |
| indexing.md | Index types, composite indexes | Performance tuning |
| optimization.md | N+1, EXPLAIN ANALYZE | Query optimization |
| migrations.md | Safe migrations, serverless DBs | Schema changes |
---
⚠️ Core Principle
---
Decision Checklist
Before designing schema:
---
Anti-Patterns
❌ Default to PostgreSQL for simple apps (SQLite may suffice)
❌ Skip indexing
❌ Use SELECT * in production
❌ Store JSON when structured data is better
❌ Ignore N+1 queries
Compétences similaires
Explorez d'autres agents de la catégorie Data, Backend & API
application-performance-performance-optimization
"Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack."
hybrid-search-implementation
Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall.
rag-implementation
Build Retrieval-Augmented Generation (RAG) systems for LLM applications with vector databases and semantic search. Use when implementing knowledge-grounded AI, building document Q&A systems, or integrating LLMs with external knowledge bases.