Lindorm
Cloud-native multi-model database with wide-column, time series, search, file, vector, graph and stream engines.
- Provider
- alibabacloud
- Kind
- NoSQL database
- Category
- Data
- Official docs
- https://www.alibabacloud.com/help/en/lindorm
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| backupEnabled | boolean | — | no | false | inherited |
| backupRetentionDays | integer | — | no | — | inherited |
| bucketing | boolean | — | no | false | inherited |
| compatibility | enum | hbase | cassandra | phoenix | opentsdb | solr | no | — | 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 |
| engine | enum | table | tsdb | search | dfs | vector | graph | stream | compute | no | table | inherited |
| instances | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| model | enum | key-value | wide-column | document | yes | — | ▸ wide-column |
| 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 | inherited |
| 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: "lindorm", component: "alibaba-lindorm" }ApsaraDB for HBasealibaba-apsaradb-hbaseApsaraDB for MongoDBalibaba-apsaradb-mongodbTablestorealibaba-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 # Lindorm: "a cloud native multi-model database service" whose engines cover wide-column # (LindormTable, HBase-compatible), time series (LindormTSDB), full-text search (LindormSearch, # Elasticsearch-compatible), distributed files (LindormDFS), vectors, graphs and streams # ("Introduction to Lindorm"). The wide-column engine is the one a design usually places. schemaVersion: "1" type: "component" id: "alibaba-lindorm" kind: "nosql-database" provider: "alibabacloud" docs: "https://www.alibabacloud.com/help/en/lindorm" defaults: managed: true model: "wide-column" properties: engine: type: "enum" values: ["table", "tsdb", "search", "dfs", "vector", "graph", "stream", "compute"] default: "table" compatibility: type: "enum" values: ["hbase", "cassandra", "phoenix", "opentsdb", "solr"]