What characterizes a document-oriented database?

What characterizes a document-oriented database?

• A. Stores data as fixed schemas in tables with normalized relationships.
• B. Stores data as flexible JSON-like documents with embedded related data.
• C. Stores data primarily as key-value pairs with little structure.
• D. Replaces relational databases entirely for all workloads.

Answer: (B)

Document-oriented databases store data as documents, usually JSON-like, where each document contains all the data for an entity and can include nested or embedded related data. There’s no fixed schema, so fields can vary between documents and the structure can evolve over time. This setup enables retrieving a whole object in a single read without needing joins, which is ideal for complex or hierarchical data. In contrast to relational databases, which organize data into tables with predefined schemas and normalized relationships, document stores embrace flexible structures and embedded data. They’re not meant to replace relational databases for every workload, but they excel in scenarios with dynamic schemas and nested data.

Document-oriented databases store data as documents, usually JSON-like, where each document contains all the data for an entity and can include nested or embedded related data. There’s no fixed schema, so fields can vary between documents and the structure can evolve over time. This setup enables retrieving a whole object in a single read without needing joins, which is ideal for complex or hierarchical data. In contrast to relational databases, which organize data into tables with predefined schemas and normalized relationships, document stores embrace flexible structures and embedded data. They’re not meant to replace relational databases for every workload, but they excel in scenarios with dynamic schemas and nested data.