Why this matters
- VaultCommerce product catalogs vary wildly: electronics have specs, apparel has sizes, groceries have expiry dates — a rigid SQL schema fights every new category.
- Interviewers ask when you'd trade joins for embedded documents and what consistency you give up.
- MongoDB is the most common document store in production Java shops; knowing its access patterns prevents expensive redesigns.
SQL (Postgres)
ACID transactions
Complex joins
Fixed schema
NoSQL
Flexible schema
Horizontal scale
Specialised access
When documents beat tables
VaultCommerce started with Postgres for orders and inventory. Product pages, however, needed nested attributes, locale-specific copy, and review snippets loaded in a single round trip. That access pattern maps naturally to documents.
Document store strengths
- Flexible schema — add
warranty_monthsto electronics withoutALTER TABLE. - Embedded data — reviews, variants, and images live inside the product document.
- Horizontal scale — shard by
category_idorseller_idwhen catalogs grow. - Developer ergonomics — JSON maps directly to API responses.
{
"_id": "prod_8842",
"name": "VaultCommerce Noise-Cancelling Headphones",
"category": "electronics",
"price": { "amount": 14999, "currency": "INR" },
"variants": [
{ "sku": "VC-HP-BLK", "color": "black", "stock": 240 },
{ "sku": "VC-HP-WHT", "color": "white", "stock": 87 }
],
"reviews": [
{ "user_id": "u_12", "rating": 5, "text": "Battery lasts all day." }
]
}
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 3 sections
- Modelling for your queries
- Indexing and consistency
- When not to use MongoDB
Test yourself
Answer these before moving on — recall is what makes it stick.