TiKV
E699798
TiKV is an open-source, distributed transactional key-value database designed for horizontal scalability and strong consistency, often used as the storage layer for cloud-native applications.
All labels observed (2)
| Label | Occurrences |
|---|---|
| TiKV canonical | 2 |
| TiKV community | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7938794 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TiKV Context triple: [Cloud Native Computing Foundation, hostsProject, TiKV]
-
A.
RocksDB
RocksDB is a high-performance, embeddable key–value store developed by Facebook, optimized for fast storage on flash and solid-state drives using a Log-Structured Merge-Tree (LSM) architecture.
-
B.
etcd
etcd is a distributed, reliable key-value store commonly used as the backing data store for configuration and state management in systems like Kubernetes.
-
C.
TokuDB
TokuDB is a high-performance storage engine for MySQL and MariaDB designed for large-scale, write-intensive workloads using Fractal Tree indexing to improve compression and insertion speed.
-
D.
RethinkDB
RethinkDB is an open-source, distributed NoSQL database designed for real-time applications by pushing live updates to clients as data changes.
-
E.
TimesTen
TimesTen is an in-memory relational database from Oracle designed for extremely low-latency, high-throughput data management and real-time analytics.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: TiKV Target entity description: TiKV is an open-source, distributed transactional key-value database designed for horizontal scalability and strong consistency, often used as the storage layer for cloud-native applications.
-
A.
CockroachDB
CockroachDB is a distributed SQL database designed for horizontal scalability, strong consistency, and high fault tolerance across multiple nodes and regions.
-
B.
RocksDB
RocksDB is a high-performance, embeddable key–value store developed by Facebook, optimized for fast storage on flash and solid-state drives using a Log-Structured Merge-Tree (LSM) architecture.
-
C.
etcd
etcd is a distributed, reliable key-value store commonly used as the backing data store for configuration and state management in systems like Kubernetes.
-
D.
TokuDB
TokuDB is a high-performance storage engine for MySQL and MariaDB designed for large-scale, write-intensive workloads using Fractal Tree indexing to improve compression and insertion speed.
-
E.
RethinkDB
RethinkDB is an open-source, distributed NoSQL database designed for real-time applications by pushing live updates to clients as data changes.
- F. None of above. chosen
Statements (88)
| Predicate | Object |
|---|---|
| instanceOf |
distributed key-value database
ⓘ
open-source software project ⓘ transactional key-value store ⓘ |
| designedFor |
cloud-native environments
ⓘ
horizontal scalability ⓘ strong consistency ⓘ |
| developedBy | PingCAP ⓘ |
| ecosystemComponentOf | Cloud Native Computing Foundation landscape ⓘ |
| hasFeature |
ACID transactions
ⓘ
Kubernetes deployment support ⓘ MVCC ⓘ Prometheus metrics ⓘ Raft consensus ⓘ Raft learner replicas ⓘ Raft-based replication ⓘ RocksDB-based storage engine ⓘ TLS encryption support ⓘ Titan key-value separation engine option ⓘ automatic data rebalancing ⓘ automatic failover ⓘ automatic sharding ⓘ backup & restore (BR) ecosystem tools ⓘ cloud-native storage ⓘ coprocessor framework ⓘ data compression ⓘ disaster recovery support ⓘ distributed GC for MVCC versions ⓘ distributed garbage collection ⓘ distributed key range management ⓘ distributed lock manager ⓘ distributed transactions ⓘ fault tolerance ⓘ gRPC-based APIs ⓘ geo-distributed deployment support ⓘ global distributed transactions via PD ⓘ high availability ⓘ horizontal scalability ⓘ hotspot scheduling ⓘ leader election via Raft ⓘ multi-tenant support via namespaces ⓘ online backup and restore ⓘ online configuration changes ⓘ online scaling ⓘ operator for Kubernetes ⓘ optimistic transactions ⓘ per-key linearizability ⓘ pessimistic transactions ⓘ placement driver integration ⓘ placement rules ⓘ range queries ⓘ raw key-value API ⓘ region merge and split ⓘ region-based data partitioning ⓘ scale-out architecture ⓘ secondary indexes via TiDB integration ⓘ shared-nothing architecture ⓘ snapshot isolation ⓘ snapshot reads ⓘ strong consistency ⓘ time-based MVCC versions ⓘ transactional key-value API ⓘ transactional semantics similar to Google Spanner and F1 ⓘ two-phase commit ⓘ |
| hasUse |
OLTP workloads
ⓘ
as a building block for distributed SQL databases ⓘ general-purpose key-value storage ⓘ storage layer for TiDB ⓘ storage layer for cloud-native applications ⓘ |
| hostedOn | GitHub ⓘ |
| maintainedBy |
TiKV community
ⓘ
linked to:
TiKV
|
| partOf | TiDB ecosystem ⓘ |
| programmingLanguage | Rust ⓘ |
| repositoryURL | https://github.com/tikv/tikv ⓘ |
| softwareLicense | Apache License 2.0 ⓘ |
| supportsConsistencyModel |
per-key linearizable reads and writes
ⓘ
strong consistency ⓘ |
| supportsDeploymentModel |
Kubernetes
ⓘ
on-premises ⓘ public cloud ⓘ |
| supportsInterface |
client libraries in multiple languages
ⓘ
gRPC ⓘ raw key-value API ⓘ transactional API ⓘ |
| supportsProgrammingLanguage | Rust ⓘ |
| usesComponent |
Placement Driver (PD)
ⓘ
Raft consensus algorithm ⓘ RocksDB ⓘ |
| writtenIn | Rust ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: TiKV Description of subject: TiKV is an open-source, distributed transactional key-value database designed for horizontal scalability and strong consistency, often used as the storage layer for cloud-native applications.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: TiKV