with one click
database-mongodb
Apply expert schema design, indexing, and performance rules for MongoDB. Use when designing MongoDB schemas, creating indexes, or optimizing NoSQL query performance.
Menu
Apply expert schema design, indexing, and performance rules for MongoDB. Use when designing MongoDB schemas, creating indexes, or optimizing NoSQL query performance.
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.
Turn an approved PRD or implementation goal into SRS/FRS technical requirements (How), architecture, contracts, and verification decisions.
Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.
| name | database-mongodb |
| description | Apply expert schema design, indexing, and performance rules for MongoDB. Use when designing MongoDB schemas, creating indexes, or optimizing NoSQL query performance. |
| metadata | {"triggers":{"files":["**/*.ts","**/*.js","**/*.json"],"keywords":["mongo","mongoose","objectid","schema","model"]}} |
DailyLog).(status, date, price) if you query status='A', sort by date, filter price > 10.See implementation examples for compound index and pagination patterns.
$text search instead of $regex for keywords. $regex slow (linear scan) unless anchored (^prefix).PROJECTION key).nReturned / keysExamined ratio of ~1. If docsExamined >> nReturned, index inefficient.Timestamp, ObjectId) for high-write workloads (creates "Hot Shards"). Use Hashed Sharding or high-cardinality natural keys.Cursor-Based Pagination: Use _id or sort-key based pagination instead of skip(). skip(10000) scans 10000 docs.
Aggregation: Prefer Aggregation Framework ($match, $group) over bringing data to client (JS).
w:1 (Ack) vs w:majority (Safe).$push with $slice or redesign using Bucket Pattern.