Database
RecognitionAmazon DocumentDB
Document database option evaluated from document access patterns, indexing, scale, and operational requirements.
Key points
- DocumentDB stores document-oriented records and supports document access patterns through a managed database.
- Indexing, query shape, scale, and compatibility requirements must be validated against the workload.
Best-known use cases
- Store semi-structured application records with document-oriented queries.
- Use a managed document database as a pipeline source or serving store.
What candidates often confuse it with
- DocumentDB is for document queries; DynamoDB is driven by modeled key access and Neptune by graph traversal.
Key takeaway
Choose DocumentDB when the serving model is document-oriented and the required query and compatibility boundaries fit.
Relevant exam tasks
- D2.1 — Task 2.1: Choose a data store
- 2.1.1 — Implement the appropriate storage services for specific cost and performance requirements (for example, Amazon Redshift, Amazon EMR, AWS Lake Formation, Amazon RDS, Amazon DynamoDB, Amazon Kinesis Data Streams, Amazon Managed Streaming for Apache Kafka [Amazon MSK]).
- 2.1.2 — Configure the appropriate storage services for specific access patterns and requirements (for example, Amazon Redshift, Amazon EMR, Lake Formation, Amazon RDS, DynamoDB).