<- Back to docs hub

Database Documentation

MongoDB structure, initialization flow, collection contracts, indexes, and seed data used by the application.

Runtime setup

Collections and schema rules

CollectionMain required fieldsNotes
usersemail, createdAtUses soft delete field deletedAt and optional updatedAt.
credittypesname, baseInterestRate, maxAmount, createdAtCatalog for available loan products and rules used by calculator and request flow.
creditrequestsemail, requestedAmount, status, createdAtStatus enum in validator: Pending, Approved, Rejected.
services(none defined in validator)Container for service catalog data used by frontend informational pages.
contactmessages(none defined in validator)Stores contact form submissions and moderation status.

Schema validators are currently configured for core operational collections and can be expanded as domain requirements evolve.

Index strategy

CollectionIndexesReason
usersemail (unique), createdAt, deletedAtFast authentication lookup, chronological listing, and soft-delete filtering.
credittypesisActive, name (unique), createdAtPublic pages and calculators filter active products frequently.
creditrequestsstatus, email, createdAt (desc)Admin dashboard and request tracking are status/date driven.
contactmessagesstatus, createdAt (desc)Operational inbox views prioritize message status and recency.

Seed data and defaults

Local operations

Resetting with -v recreates the volume and reruns initialization scripts from scratch.