IBM Cloudant
Managed JSON document store where every node accepts reads and writes and the application reconciles conflicting revisions.
- Provider
- ibm
- Kind
- NoSQL database
- Category
- Data
- Official docs
- https://cloud.ibm.com/docs/Cloudant
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| 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 | — | ▸ app-merge |
| consistency | enum | eventual | tunable | strong | no | eventual | ▸ eventual |
| encryptionAtRest | boolean | — | no | false | ▸ true |
| instances | integer | — | no | — | inherited |
| keyManagement | enum | provider-managed | customer-managed | no | provider-managed | inherited |
| managed | boolean | — | no | false | ▸ true |
| minimumTlsVersion | enum | 1.2 | 1.3 | no | 1.2 | inherited |
| 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 |
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: "cloudant", component: "ibm-cloudant" }ApsaraDB for HBasealibaba-apsaradb-hbaseApsaraDB for MongoDBalibaba-apsaradb-mongodbLindormalibaba-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-database
and 6 more → NoSQL database page# yaml-language-server: $schema=../../schema/component.schema.json # IBM Cloudant: a managed JSON document store with a primary-primary setup in which "every node # can accept both writes and reads" and updates are "eventually seen by other parts of the # system" ("CAP Theorem"). Conflicting revisions are not resolved for you: "your application # must identify all the potential changes, and reconcile them" ("Conflicts"). "Security" states # that all stored data is encrypted at rest with AES-256 under IBM-managed keys, that BYOK # through Key Protect is a Dedicated Hardware plan option, and that TLS 1.2 is the minimum. schemaVersion: "1" type: "component" id: "ibm-cloudant" kind: "nosql-database" provider: "ibm" docs: "https://cloud.ibm.com/docs/Cloudant" defaults: managed: true model: "document" consistency: "eventual" replication: "single-region" conflictResolution: "app-merge" encryptionAtRest: true properties: keyManagement: type: "enum" values: ["provider-managed", "customer-managed"] default: "provider-managed" minimumTlsVersion: type: "enum" values: ["1.2", "1.3"] default: "1.2"