Document Indexes and Performance Strategy #36
Labels
No labels
CI/CD
MongoDB
PostgreSQL
api
authentication
bug
documentation
duplicate
enhancement
example issue
fix
good first issue
help wanted
high-level requirement
infrastructure
invalid
low-level requirement
medium-level requirement
question
security
test
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AndreFerreira5/starranja#36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
To meet the non-functional requirement RNF03 (response time < 3s) and support real-time dashboard queries (RF10), we must define a clear indexing strategy. Indexes are critical for fast query performance in MongoDB.
This task involves reviewing all collections and identifying the fields that will be queried most often.
Tasks
clientscollection (e.g.,nif(unique),phone,name).vehiclescollection (e.g.,licensePlate(unique),clientId).workOrderscollection (e.g.,status,vehicleId,clientId,mechanicsIds,entryDate).invoicescollection (e.g.,workOrderId,clientId,invoiceDate).workOrderson{ status: 1, entryDate: -1 }).