Suggest an editImprove this articleRefine the answer for “Why is MongoDB called a document-oriented database?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)Because MongoDB stores data as documents rather than table rows: each document is a JSON-like object (BSON) with its own structure that fully describes an entity, and documents are grouped into collections with no rigid schema. **Key point:** different documents inside the same collection can have different sets of fields, and nested structures are stored right inside the document with no need for a `JOIN` - one document maps to one entity in the application.Shown above the full answer for quick recall.Answer (EN)ImageBecause MongoDB stores data **as documents**, not table rows. Each document is a JSON-like object (BSON) with its own structure that fully describes an entity. ### The core idea of the document approach - data is stored as **self-contained documents** (e.g. a user with all its nested fields) - documents are grouped into **collections** (analogous to tables, but with no rigid schema) - different documents within the same collection **can have different sets of fields** An example document in MongoDB: ```json { "name": "Alice", "age": 25, "skills": ["mongo", "node"], "address": { "city": "Berlin", "street": "Main St" } } ``` ### Why this is convenient - nested structures can be stored right inside the document (no JOIN needed) - the data model is easy and fast to change - one document = one entity in the application (a good fit for the JSON world of the web and APIs) **Summary:** MongoDB is called document-oriented because its basic storage unit isn't a table row, it's a document representing an entire entity in a JSON structure.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.