Document database implementation for flexible schema applications. Use when building content management, user profiles, catalogs, or event logging. Covers MongoDB (primary), DynamoDB, Firestore, schema design patterns, indexing strategies, and aggregation pipelines.
Guide NoSQL document database selection and implementation for flexible schema applications across Python, TypeScript, Rust, and Go.
Use document databases when applications need:
DEPLOYMENT ENVIRONMENT?
├── AWS-Native Application → DynamoDB
│ ✓ Serverless, auto-scaling, single-digit ms latency
│ ✗ Limited query flexibility
│
├── Firebase/GCP Ecosystem → Firestore
│ ✓ Real-time sync, offline support, mobile-first
│ ✗ More expensive for heavy reads
│
└── General-Purpose/Complex Queries → MongoDB
✓ Rich aggregation, full-text search, vector search
✓ ACID transactions, self-hosted or managed
| Database | Best For | Latency | Max Item | Query Language |
|---|---|---|---|---|
| MongoDB | General-purpose, complex queries | 1-5ms | 16MB | MQL (rich) |
| DynamoDB | AWS serverless, predictable performance | <10ms | 400KB | PartiQL (limited) |
| Firestore | Real-time apps, mobile-first | 50-200ms | 1MB | Firebase queries |
See references/mongodb.md for MongoDB details
See references/dynamodb.md for DynamoDB single-table design
See references/firestore.md for Firestore real-time patterns
Use the decision matrix in references/schema-design-patterns.md
Quick guide:
| Relationship | Pattern | Example |
|---|---|---|
| One-to-Few | Embed | User addresses (2-3 max) |
| One-to-Many | Hybrid | Blog posts → comments |
| One-to-Millions | Reference | User → events (logging) |
| Many-to-Many | Reference | Products ↔ Categories |
// User with embedded addresses
{
_id: ObjectId("..."),
email: "[email protected]",
name: "Jane Doe",
addresses: [
{
type: "home",
street: "123 Main St",
city: "Boston",
default: true
}
],
preferences: {
theme: "dark",
notifications: { email: true, sms: false }
}
}
// Orders reference products
{
_id: ObjectId("..."),
userId: ObjectId("..."),
items: [
{
productId: ObjectId("..."), // Reference
priceAtPurchase: 49.99, // Denormalize (historical)
quantity: 2
}
],
totalAmount: 99.98
}
When to denormalize:
// 1. Single field (unique email)
db.users.createIndex({ email: 1 }, { unique: true })
// 2. Compound index (ORDER MATTERS!)
db.orders.createIndex({ status: 1, createdAt: -1 })
// 3. Partial index (index subset)
db.orders.createIndex(
{ userId: 1 },
{ partialFilterExpression: { status: { $eq: "pending" }}}
)
// 4. TTL index (auto-delete after 30 days)
db.sessions.createIndex(
{ createdAt: 1 },
{ expireAfterSeconds: 2592000 }
)
// 5. Text index (full-text search)
db.articles.createIndex({
title: "text",
content: "text"
})
Index Best Practices:
explain() to verify index usageValidate indexes with the script:
python scripts/validate_indexes.py
See references/indexing-strategies.md for complete guide.
Key Operators: $match (filter), $group (aggregate), $lookup (join), $unwind (arrays), $project (reshape)
For complete pipeline patterns and examples, see: references/aggregation-patterns.md
Design for access patterns using PK/SK patterns. Store multiple entity types in one table with composite keys.
For complete single-table design patterns and GSI strategies, see: references/dynamodb.md
Use onSnapshot() for real-time listeners and Firestore security rules for access control.
For complete real-time patterns and security rules, see: references/firestore.md
Complete implementations available in examples/ directory:
examples/mongodb-fastapi/ - Python FastAPI + MongoDBexamples/mongodb-nextjs/ - TypeScript Next.js + MongoDBexamples/dynamodb-serverless/ - Python Lambda + DynamoDBexamples/firestore-react/ - React + Firestore real-timeFor integration examples, see: references/skill-integrations.md
Key practices:
.explain())For complete optimization guide, see: references/performance.md
Pagination: Use cursor-based pagination for large datasets (recommended over offset) Soft Deletes: Mark as deleted with timestamp instead of removing Audit Logs: Store version history within documents
For implementation details, see: references/common-patterns.md
# Run validation script
python scripts/validate_indexes.py --db myapp --collection orders
# Output:
# ✓ Query { status: "pending" } covered by index status_1
# ✗ Query { userId: "..." } missing index - add: { userId: 1 }
# Analyze schema patterns
python scripts/analyze_schema.py --db myapp
# Output:
# Collection: users
# - Average document size: 2.4 KB
# - Embedding ratio: 87% (addresses, preferences)
# - Reference ratio: 13% (orderIds)
# Recommendation: Good balance
Unbounded Arrays: Limit embedded arrays (use references for large collections) Over-Indexing: Only index queried fields (indexes slow writes) DynamoDB Scans: Always use Query with partition key (avoid Scan)
For detailed anti-patterns, see: references/anti-patterns.md
# MongoDB
pip install motor pymongo
# DynamoDB
pip install boto3
# Firestore
pip install firebase-admin
# MongoDB
npm install mongodb
# DynamoDB
npm install @aws-sdk/client-dynamodb @aws-sdk/util-dynamodb
# Firestore
npm install firebase firebase-admin
# MongoDB
mongodb = "2.8"
# DynamoDB
aws-sdk-dynamodb = "1.0"
# MongoDB
go get go.mongodb.org/mongo-driver
# DynamoDB
go get github.com/aws/aws-sdk-go-v2/service/dynamodb
Database-Specific Guides:
references/mongodb.md - Complete MongoDB documentationreferences/dynamodb.md - DynamoDB single-table patternsreferences/firestore.md - Firestore real-time guidePattern Guides:
references/schema-design-patterns.md - Embedding vs referencing decisionsreferences/indexing-strategies.md - Index optimizationreferences/aggregation-patterns.md - MongoDB pipeline cookbookreferences/common-patterns.md - Pagination, soft deletes, audit logsreferences/anti-patterns.md - Mistakes to avoidreferences/performance.md - Query optimizationreferences/skill-integrations.md - Frontend skill integrationExamples: examples/mongodb-fastapi/, examples/mongodb-nextjs/, examples/dynamodb-serverless/, examples/firestore-react/