TiKV

Distributed transactional key-value store with Raft-replicated Regions.

Provider
default
Category
Data
Properties · 5 set by this component
propertytypevaluesrequiredkind defaultthis component
api · component propertyenumraw | transactionalno—inherited
backupEnabledboolean—nofalseinherited
backupRetentionDaysinteger—no—inherited
bucketing · advancedboolean—nofalseinherited
conflictResolutionenumnone | last-writer-wins | vector-clock | app-mergeno—inherited
consistencyenumeventual | tunable | strongnoeventual▸ strong
encryptionAtRestboolean—nofalse▸ false
instancesinteger—no—inherited
managedboolean—nofalseinherited
modelenumkey-value | wide-column | documentyes—▸ key-value
partitionKeystring—no—inherited
quorumReads · advancedinteger—no—inherited
quorumWrites · advancedinteger—no—inherited
replicationenumsingle-region | multi-region-single-leader | multi-region-multi-leader | leaderlessnosingle-region▸ single-region
replicationFactorinteger—no—▸ 3
tombstoneTtlDays · advancedinteger—no—inherited
version · component propertystring—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-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: "tikv", component: "tikv" }
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-databaseOrientDBorientdbnosql-databaseRavenDBravendbnosql-databaseRethinkDBrethinkdbnosql-databaseRiak KVriaknosql-databaseScyllaDBscylladbnosql-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
# TiKV: distributed transactional key-value store. Data is split into Regions, each a Raft group
# whose default replica count (PD max-replicas) is 3; transactions follow the Percolator model (TiKV "Architecture", "PD Config").
schemaVersion: "1"
type: "component"
id: "tikv"
kind: "nosql-database"
provider: "default"
docs: "https://tikv.org/docs/latest/reference/architecture/overview/"
defaults:
  model: "key-value"
  consistency: "strong"
  replication: "single-region"
  replicationFactor: 3
  encryptionAtRest: false
properties:
  version:
    type: "string"
  api:
    type: "enum"
    values: ["raw", "transactional"]

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