Amazon DocumentDB

MongoDB-compatible document cluster whose storage keeps six copies of the data across three Availability Zones.

Provider: aws
Kind: NoSQL database
Category: Data
Official docs: https://docs.aws.amazon.com/documentdb/latest/developerguide/encryption-at-rest.html

Properties · 8 set by this component

property	type	values	required	kind default	this component
backupEnabled	boolean	—	no	false	▸ true
backupRetentionDays	integer	—	no	—	▸ 1
bucketing · advanced	boolean	—	no	false	inherited
clusterType · component property	enum	instance-based \| elastic	no	instance-based	inherited
conflictResolution	enum	none \| last-writer-wins \| vector-clock \| app-merge	no	—	inherited
consistency	enum	eventual \| tunable \| strong	no	eventual	▸ tunable
encryptionAtRest	boolean	—	no	false	▸ true
globalCluster · component property	boolean	—	no	false	inherited
instances	integer	—	no	—	inherited
managed	boolean	—	no	false	▸ true
model	enum	key-value \| wide-column \| document	yes	—	▸ document
partitionKey	string	—	no	—	inherited
quorumReads · advanced	integer	—	no	—	inherited
quorumWrites · advanced	integer	—	no	—	inherited
replication	enum	single-region \| multi-region-single-leader \| multi-region-multi-leader \| leaderless	no	single-region	▸ single-region
replicationFactor	integer	—	no	—	▸ 6
storageConfiguration · component property	enum	standard \| io-optimized	no	standard	inherited
tls · component property	boolean	—	no	true	inherited
tombstoneTtlDays · advanced	integer	—	no	—	inherited

Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

Multi-leader store without a conflict policywarning

multi-leader-store-without-conflict-policy

Multi-leader replication accepts concurrent writes in several regions. With no conflict resolution policy declared, divergent replicas are reconciled by accident rather than by design.

— all of these hold:
— the node's `replication` is "multi-region-multi-leader"
— any of these hold:
— the node's `conflictResolution` has no value
— the node's `conflictResolution` is "none"

Read-heavy datastore without a cachewarning

read-heavy-path-without-cache

The design states a read-heavy workload and application servers read this datastore directly, yet the design has no cache anywhere. Every read pays a database round trip.

— all of these hold:
— the design requirement `traffic.readWriteRatio` is a number greater than 10
— the node has at least one synchronous incoming edge from an app-server
— this does not hold:
— the design contains a node of kind cache

Use it in a design

nodes:
  - { id: "documentdb", component: "aws-documentdb" }

Other NoSQL database products · 46

ApsaraDB for HBasealibaba-apsaradb-hbasealibabacloudnosql-database ApsaraDB for MongoDBalibaba-apsaradb-mongodbalibabacloudnosql-database Lindormalibaba-lindormalibabacloudnosql-database Tablestorealibaba-tablestorealibabacloudnosql-database Amazon CloudFront KeyValueStoreaws-cloudfront-keyvaluestoreawsnosql-database Amazon Cognito Syncaws-cognito-syncawsnosql-database AWS HealthLakeaws-healthlakeawsnosql-database Amazon Keyspaces (for Apache Cassandra)aws-keyspacesawsnosql-database Amazon DynamoDBdynamodbawsnosql-database Azure Cosmos DBazure-cosmos-dbazurenosql-database Azure DocumentDBazure-documentdbazurenosql-database Azure Health Data Servicesazure-health-data-servicesazurenosql-database Azure Managed Instance for Apache Cassandraazure-managed-cassandraazurenosql-database Azure Table Storageazure-table-storageazurenosql-database Workers KVcloudflare-workers-kvcloudflarenosql-database Apache Accumuloaccumulonosql-database Aerospike Databaseaerospikenosql-database Apache Cassandracassandranosql-database Couchbasecouchbasenosql-database Apache CouchDBcouchdbnosql-database DataStax Enterprisedatastax-enterprisenosql-database FoundationDBfoundationdbnosql-database Apache HBasehbasenosql-database MarkLogic Servermarklogicnosql-database MongoDBmongodbnosql-database MongoDB Atlasmongodb-atlasnosql-database Generic NoSQL databasenosql-databasenosql-database NoSQL storenosql-storenosql-database OrientDBorientdbnosql-database RavenDBravendbnosql-database RethinkDBrethinkdbnosql-database Riak KVriaknosql-database ScyllaDBscylladbnosql-database TiKVtikvnosql-database YDBydbnosql-database Google Cloud Bigtablebigtablegcpnosql-database Google Cloud Firestorefirestoregcpnosql-database Cloud Healthcare APIgoogle-cloud-healthcare-apigcpnosql-database Firebase Realtime Databasegoogle-firebase-realtime-databasegcpnosql-database Firestore in Datastore modegoogle-firestore-datastore-modegcpnosql-database

and 6 more → NoSQL database page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Amazon DocumentDB (with MongoDB compatibility): cluster whose storage keeps six copies of the data
3# across three Availability Zones. "Encrypting Amazon DocumentDB data at rest" says console-created
4# clusters have encryption at rest enabled by default and that backups are always enabled for at least
5# 1 day; "Encrypting data in transit" says TLS is enabled by default for newly created clusters.
6schemaVersion: "1"
7type: "component"
8id: "aws-documentdb"
9kind: "nosql-database"
10provider: "aws"
11docs: "https://docs.aws.amazon.com/documentdb/latest/developerguide/encryption-at-rest.html"
12defaults:
13  managed: true
14  model: "document"
15  consistency: "tunable"
16  replication: "single-region"
17  replicationFactor: 6
18  backupEnabled: true
19  backupRetentionDays: 1
20  encryptionAtRest: true
21properties:
22  clusterType:
23    type: "enum"
24    values: ["instance-based", "elastic"]
25    default: "instance-based"
26  tls:
27    type: "boolean"
28    default: true
29  storageConfiguration:
30    type: "enum"
31    values: ["standard", "io-optimized"]
32    default: "standard"
33  globalCluster:
34    type: "boolean"
35    default: false

The same page as markdown, for an agent: /catalogue/components/aws-documentdb.md