ApsaraDB for MongoDB
Managed MongoDB-compatible document database deployed as a standalone node, a replica set or a sharded cluster.
- Provider
- alibabacloud
- Kind
- NoSQL database
- Category
- Data
- Official docs
- https://www.alibabacloud.com/help/en/mongodb/
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| architecture | enum | standalone | replica-set | sharded-cluster | no | — | inherited |
| auditLog | boolean | — | no | — | inherited |
| backupEnabled | boolean | — | no | false | inherited |
| backupRetentionDays | integer | — | no | — | inherited |
| bucketing | boolean | — | no | false | inherited |
| conflictResolution | enum | none | last-writer-wins | vector-clock | app-merge | no | — | inherited |
| consistency | enum | eventual | tunable | strong | no | eventual | inherited |
| encryptionAtRest | 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 | integer | — | no | — | inherited |
| quorumWrites | integer | — | no | — | inherited |
| replication | enum | single-region | multi-region-single-leader | multi-region-multi-leader | leaderless | no | single-region | ▸ single-region |
| replicationFactor | integer | — | no | — | inherited |
| tombstoneTtlDays | integer | — | no | — | inherited |
| transparentDataEncryption | boolean | — | no | — | inherited |
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-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-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
nodes:
- { id: "apsaradb-mongodb", component: "alibaba-apsaradb-mongodb" }ApsaraDB for HBasealibaba-apsaradb-hbaseLindormalibaba-lindormTablestorealibaba-tablestoreAmazon CloudFront KeyValueStoreaws-cloudfront-keyvaluestoreAmazon Cognito Syncaws-cognito-syncAmazon DocumentDBaws-documentdbAWS HealthLakeaws-healthlakeAmazon Keyspaces (for Apache Cassandra)aws-keyspacesAmazon DynamoDBdynamodbAzure Cosmos DBazure-cosmos-dbAzure DocumentDBazure-documentdbAzure Health Data Servicesazure-health-data-servicesAzure Managed Instance for Apache Cassandraazure-managed-cassandraAzure Table Storageazure-table-storageWorkers KVcloudflare-workers-kvApache AccumuloaccumuloAerospike DatabaseaerospikeApache CassandracassandraCouchbasecouchbaseApache CouchDBcouchdbDataStax Enterprisedatastax-enterpriseFoundationDBfoundationdbApache HBasehbaseMarkLogic ServermarklogicMongoDBmongodbMongoDB Atlasmongodb-atlasGeneric NoSQL databasenosql-databaseNoSQL storenosql-storeOrientDBorientdbRavenDBravendbRethinkDBrethinkdbRiak KVriakScyllaDBscylladbTiKVtikvYDBydbGoogle Cloud BigtablebigtableGoogle Cloud FirestorefirestoreCloud Healthcare APIgoogle-cloud-healthcare-apiFirebase Realtime Databasegoogle-firebase-realtime-databaseFirestore in Datastore modegoogle-firestore-datastore-mode
and 6 more → NoSQL database page# yaml-language-server: $schema=../../schema/component.schema.json # ApsaraDB for MongoDB: managed MongoDB-compatible document database. "What is ApsaraDB for MongoDB?" # describes a document store built on the distributed Apsara system that keeps JSON-like documents and # uses a multi-node architecture for high availability within a region; the same page lists transparent # data encryption (TDE) among the security features you turn on, alongside RAM authorization, audit # logs, network isolation, whitelists and password authentication. "Deploy MongoDB Replica Sets & # Sharded Clusters" gives the standalone, replica set and sharded cluster architectures. schemaVersion: "1" type: "component" id: "alibaba-apsaradb-mongodb" kind: "nosql-database" provider: "alibabacloud" docs: "https://www.alibabacloud.com/help/en/mongodb/" defaults: managed: true model: "document" replication: "single-region" properties: architecture: type: "enum" values: ["standalone", "replica-set", "sharded-cluster"] transparentDataEncryption: type: "boolean" auditLog: type: "boolean"