OrientDB

Multi-model document and graph store replicating between master servers at a majority write quorum.

Provider
default
Category
Data
Properties · 4 set by this component
propertytypevaluesrequiredkind defaultthis component
autoDeploy · component propertyboolean—notrueinherited
backupEnabledboolean—nofalseinherited
backupRetentionDaysinteger—no—inherited
bucketing · advancedboolean—nofalseinherited
conflictResolutionenumnone | last-writer-wins | vector-clock | app-mergeno—inherited
consistencyenumeventual | tunable | strongnoeventual▸ tunable
encryptionAtRestboolean—nofalseinherited
instancesinteger—no—inherited
managedboolean—nofalseinherited
modelenumkey-value | wide-column | documentyes—▸ document
partitionKeystring—no—inherited
quorumReads · advancedinteger—no—▸ 1
quorumWrites · advancedinteger—no—inherited
replicationenumsingle-region | multi-region-single-leader | multi-region-multi-leader | leaderlessnosingle-region▸ single-region
replicationFactorinteger—no—inherited
tombstoneTtlDays · advancedinteger—no—inherited
writeQuorum · component propertyenumone | majority | allnomajorityinherited
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-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
Use it in a design
nodes:
  - { id: "orientdb", component: "orientdb" }
Other NoSQL database products · 46
ApsaraDB for HBasealibaba-apsaradb-hbasealibabacloudnosql-databaseApsaraDB for MongoDBalibaba-apsaradb-mongodbalibabacloudnosql-databaseLindormalibaba-lindormalibabacloudnosql-databaseTablestorealibaba-tablestorealibabacloudnosql-databaseAmazon CloudFront KeyValueStoreaws-cloudfront-keyvaluestoreawsnosql-databaseAmazon Cognito Syncaws-cognito-syncawsnosql-databaseAmazon DocumentDBaws-documentdbawsnosql-databaseAWS HealthLakeaws-healthlakeawsnosql-databaseAmazon Keyspaces (for Apache Cassandra)aws-keyspacesawsnosql-databaseAmazon DynamoDBdynamodbawsnosql-databaseAzure Cosmos DBazure-cosmos-dbazurenosql-databaseAzure DocumentDBazure-documentdbazurenosql-databaseAzure Health Data Servicesazure-health-data-servicesazurenosql-databaseAzure Managed Instance for Apache Cassandraazure-managed-cassandraazurenosql-databaseAzure Table Storageazure-table-storageazurenosql-databaseWorkers KVcloudflare-workers-kvcloudflarenosql-databaseApache Accumuloaccumulonosql-databaseAerospike Databaseaerospikenosql-databaseApache Cassandracassandranosql-databaseCouchbasecouchbasenosql-databaseApache CouchDBcouchdbnosql-databaseDataStax Enterprisedatastax-enterprisenosql-databaseFoundationDBfoundationdbnosql-databaseApache HBasehbasenosql-databaseMarkLogic Servermarklogicnosql-databaseMongoDBmongodbnosql-databaseMongoDB Atlasmongodb-atlasnosql-databaseGeneric NoSQL databasenosql-databasenosql-databaseNoSQL storenosql-storenosql-databaseRavenDBravendbnosql-databaseRethinkDBrethinkdbnosql-databaseRiak KVriaknosql-databaseScyllaDBscylladbnosql-databaseTiKVtikvnosql-databaseYDBydbnosql-databaseGoogle Cloud Bigtablebigtablegcpnosql-databaseGoogle Cloud Firestorefirestoregcpnosql-databaseCloud Healthcare APIgoogle-cloud-healthcare-apigcpnosql-databaseFirebase Realtime Databasegoogle-firebase-realtime-databasegcpnosql-databaseFirestore in Datastore modegoogle-firestore-datastore-modegcpnosql-database
and 6 more → NoSQL database page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# OrientDB: multi-model document and graph store. Every server joins as a master and the shipped
# distributed configuration reads at quorum 1 and writes at a majority
# ("Distributed configuration", "Distributed architecture").
schemaVersion: "1"
type: "component"
id: "orientdb"
kind: "nosql-database"
provider: "default"
docs: "https://orientdb.dev/docs/3.2.x/distributed/Distributed-Configuration.html"
defaults:
  model: "document"
  consistency: "tunable"
  replication: "single-region"
  quorumReads: 1
properties:
  writeQuorum:
    type: "enum"
    values: ["one", "majority", "all"]
    default: "majority"
  autoDeploy:
    type: "boolean"
    default: true

The same page as markdown, for an agent: /catalogue/components/orientdb.md