Basic Information
| Field | Details |
|---|---|
| English name | Amazon DocumentDB (with MongoDB compatibility) |
| Full name | Amazon DocumentDB (with MongoDB compatibility) |
| Chinese description | 托管文档数据库 |
| Japanese description | マネージドドキュメントデータベース |
| Exam frequency | ⭐⭐ |
| Often confused with | DynamoDB / MongoDB / Neptune |
In one sentence
DocumentDB fits complex documents with nested attributes, arrays, and records that do not share identical fields.
Core purpose
- Use cases include content management, product catalogs, user profiles, personalization, and mobile backends.
- Applications can use compatible MongoDB drivers and APIs, but must validate versions, commands, and operators.
- It provides automatically growing storage, backups, read replicas, and enterprise security.
Exam focus
- MongoDB compatibility, complex JSON, nested documents, or flexible schemas point to DocumentDB.
- DynamoDB emphasizes primary-key access patterns, serverless scale, and low latency.
- Neptune traverses relationships; RDS provides SQL, joins, and transactions.
Common misconceptions
- A database document is not a Word or PDF file.
- MongoDB compatibility does not mean every MongoDB feature is identical.
Key takeaway
Complex JSON + nested attributes + MongoDB compatibility → DocumentDB.
Related services
DynamoDB, Neptune, DMS, AWS Backup, VPC, KMS.