7e199944da
* Update title tags and meta desc for Templates * Update title tags and meta desc for Learn * Update title tags, meta desc, and H1s for Case Studies * Update themes/default/content/learn/abstraction-encapsulation/_index.md Co-authored-by: susan evans <susan.ra.evans@gmail.com> * Update themes/default/content/learn/embedding-pulumi/_index.md Co-authored-by: susan evans <susan.ra.evans@gmail.com> * Update themes/default/content/learn/embedding-pulumi/building-api/index.md Co-authored-by: susan evans <susan.ra.evans@gmail.com> * Update themes/default/content/learn/building-with-pulumi/stack-references/index.md Co-authored-by: Sean Holung <sean.holung@gmail.com> * Update themes/default/content/templates/container-service/_index.md Co-authored-by: Sean Holung <sean.holung@gmail.com> * Update themes/default/content/templates/kubernetes/_index.md Co-authored-by: Sean Holung <sean.holung@gmail.com> * Update themes/default/content/templates/serverless-application/_index.md Co-authored-by: Sean Holung <sean.holung@gmail.com> * Update themes/default/content/templates/virtual-machine/_index.md Co-authored-by: Sean Holung <sean.holung@gmail.com> * Update themes/default/content/templates/static-website/_index.md Co-authored-by: Sean Holung <sean.holung@gmail.com> * Update atlassian.md * Update index.md --------- Co-authored-by: susan evans <susan.ra.evans@gmail.com> Co-authored-by: Sean Holung <sean.holung@gmail.com>
21 lines
1.7 KiB
Markdown
21 lines
1.7 KiB
Markdown
---
|
|
title_tag: What is a Document Oriented Database?
|
|
title: Document Oriented Database
|
|
meta_desc: A documented-oriented database is a class of NoSQL database that stores and queries data in the form of documents, usually JSON.
|
|
layout: glossary/single
|
|
---
|
|
|
|
## Definition
|
|
|
|
A document-oriented database is a class of NoSQL database that stores and queries data in the form of documents, usually JSON but sometimes also XML or YAML. Unlike a traditional relational database, objects within a document-based database are stored completely within one document, rather than across multiple tables. As a result, the concept of “joins” is not usually present. This model allows developers to query the database programmatically in a similar fashion to how they already access data within the application code.
|
|
|
|
Conceptually, you can think of a document as roughly equivalent to an object in your programming language. The structure is similar (or identical), and documents are not required to conform to a specific schema. For example, you may have a class of document called “books.” Each “book” object is not required to contain the same keys; one may include a “co-author” key, but the next may not. This allows for a lot of flexibility with certain types of data.
|
|
|
|
### Use Cases
|
|
|
|
Because of the flexibility and speed that document databases allow, they are a great choice for any application that relies on user profiles, content management systems, product information, and even real-time big data analytics.
|
|
|
|
### Examples
|
|
|
|
[DocumentDB](https://aws.amazon.com/documentdb/), [CosmosDB](https://azure.microsoft.com/en-us/services/cosmos-db/), [Firestore](https://firebase.google.com/docs/firestore), [MongoDB](https://www.mongodb.com/)
|