awesome-repositories.com
Blog
awesome-repositories.com

Entdecke die besten Open-Source-Repositories mit KI-gestützter Suche.

EntdeckenKuratierte SuchenOpen-Source-AlternativenSelf-hosted SoftwareBlogSitemap
ProjektÜber unsRanking-MethodikPresseMCP-Server
RechtlichesDatenschutzAGB
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·
pingcap avatar

pingcap/tikv

0
View on GitHub↗
16,724 Stars·2,289 Forks·Rust·Apache-2.0·6 Aufrufetikv.org↗

Tikv

TiKV is a cloud-native distributed transactional key-value store and storage engine. It provides a distributed database designed for horizontal scalability and strong consistency across a cluster of physical nodes.

The system uses a Raft-based consensus mechanism to maintain data availability and state synchronization. It ensures ACID compliance for distributed transactions through a two-phase commit workflow and manages data distribution via multi-Raft sharding.

The engine handles massive datasets using automated range splitting and cluster load balancing to distribute data across different physical zones or geographic regions. To reduce network latency, it employs a coprocessor for distributed computing, allowing filtering and aggregation logic to execute directly on storage nodes. Local data persistence is managed via a log-structured merge-tree engine.

Features

  • Distributed Key-Value Stores - Provides a consistent and replicated distributed key-value store designed to maintain a reliable source of truth across a cluster.
  • Distributed Consensus Stores - Provides a distributed transactional key-value store that maintains consistent state across nodes using Raft consensus.
  • Data Replication Strategies - Copies data across multiple nodes in consensus groups to ensure operational continuity and fault tolerance during node failures.
  • Cloud-Native Databases - Engineered as a cloud-native database with support for geographic data distribution and seamless horizontal scaling.
  • Multi-Raft Sharding - Divides the keyspace into small ranges, each managed by its own independent Raft consensus group for horizontal scalability.
  • Consensus Algorithms - Maintains a consistent view of data across all nodes using a Raft-based consensus algorithm to prevent state divergence.
  • Distributed Storage Engines - Provides a storage system that shards data across multiple physical nodes with automated balancing and replication.
  • Distributed Transaction Processing - Stores key-value data using a distributed layer that guarantees ACID compliance for all transactional operations via consensus protocols.
  • Horizontal Scaling - Distributes data across multiple nodes using automated sharding and migration to scale storage and throughput horizontally.
  • Log-Structured Merge-Trees - Uses a log-structured merge-tree engine for high-throughput local data persistence on individual nodes.
  • Raft Consensus Implementations - Maintains data consistency and availability by synchronizing a replicated log across storage nodes using the Raft protocol.
  • Two-Phase Commit Protocols - Ensures ACID compliance across distributed shards using a two-phase commit coordinator to manage prepare and commit workflows.
  • Distributed Transaction Management - Handles complex data operations across multiple nodes while ensuring ACID compliance and strict data consistency.
  • Dynamic Shard Splitting - Automatically divides oversized data shards into smaller pieces to balance load and manage storage growth.
  • Cluster Load Balancing - Automatically redistributes data ranges across the cluster to balance storage and compute load across physical nodes.
  • Cross-Zone Data Distribution - Distributes data copies across specific physical zones or geographies to ensure high availability and disaster recovery.
  • Coprocessors - Implements a coprocessor for executing filtering and aggregation logic directly on storage nodes to minimize network latency.
  • Distributed Computing - Executes filtering and aggregation logic directly on storage nodes to reduce data transfer over the network.
  • Regional Replication - Spreads data copies across different physical locations to ensure high availability and protection against regional disasters.
  • Storage-Side Computation - Processes data directly on storage nodes using a coprocessor to reduce network traffic and lower system latency.
  • Key-Value Stores - Distributed key-value database powered by Rust.

Star-Verlauf

Star-Verlauf für pingcap/tikvStar-Verlauf für pingcap/tikv

KI-Suche

Entdecke weitere awesome Repositories

Beschreibe in einfachen Worten, was du brauchst — die KI bewertet tausende kuratierte Open-Source-Projekte nach Relevanz.

Start searching with AI

Häufig gestellte Fragen

Was macht pingcap/tikv?

TiKV is a cloud-native distributed transactional key-value store and storage engine. It provides a distributed database designed for horizontal scalability and strong consistency across a cluster of physical nodes.

Was sind die Hauptfunktionen von pingcap/tikv?

Die Hauptfunktionen von pingcap/tikv sind: Distributed Key-Value Stores, Distributed Consensus Stores, Data Replication Strategies, Cloud-Native Databases, Multi-Raft Sharding, Consensus Algorithms, Distributed Storage Engines, Distributed Transaction Processing.

Welche Open-Source-Alternativen gibt es zu pingcap/tikv?

Open-Source-Alternativen zu pingcap/tikv sind unter anderem: hazelcast/hazelcast — Hazelcast is a distributed data platform that combines an in-memory data grid with a stream processing engine to… talent-plan/tinykv — TinyKV is a distributed key-value store designed for storing and retrieving data across multiple nodes with high… sofastack/sofa-jraft — sofa-jraft is a Java implementation of the Raft consensus algorithm. It serves as a distributed consensus engine and… oceanbase/oceanbase — OceanBase is a distributed SQL database designed for high availability and strong consistency across multiple nodes… vesoft-inc/nebula — Nebula is a distributed graph database designed for storing and querying massive volumes of interconnected vertices… yugabyte/yugabyte-db — YugabyteDB is a distributed SQL database and relational data store designed for horizontal scalability and high…

Open-Source-Alternativen zu Tikv

Ähnliche Open-Source-Projekte, sortiert nach der Anzahl der gemeinsamen Funktionen mit Tikv.
  • hazelcast/hazelcastAvatar von hazelcast

    hazelcast/hazelcast

    6,570Auf GitHub ansehen↗

    Hazelcast is a distributed data platform that combines an in-memory data grid with a stream processing engine to support real-time analytics and event-driven applications. It functions as a partitioned, distributed key-value store that replicates data across cluster nodes to provide low-latency access and high availability. The platform also serves as a distributed SQL query engine, allowing users to execute standard SQL statements against both in-memory datasets and external data sources. What distinguishes Hazelcast is its use of a distributed consensus subsystem to maintain strongly consis

    Javabig-datacachingdata-in-motion
    Auf GitHub ansehen↗6,570
  • talent-plan/tinykvAvatar von talent-plan

    talent-plan/tinykv

    3,938Auf GitHub ansehen↗

    TinyKV is a distributed key-value store designed for storing and retrieving data across multiple nodes with high availability. It functions as a distributed database system that incorporates a dedicated key-value storage engine for raw data persistence and retrieval on individual nodes. The project includes a Raft consensus engine to ensure data consistency and fault tolerance across a cluster of servers. It also features a distributed transaction manager that coordinates atomic commits and concurrency control to maintain data integrity across shards. The system covers cluster membership man

    Go
    Auf GitHub ansehen↗3,938
  • sofastack/sofa-jraftAvatar von sofastack

    sofastack/sofa-jraft

    3,806Auf GitHub ansehen↗

    sofa-jraft is a Java implementation of the Raft consensus algorithm. It serves as a distributed consensus engine and linearizable state machine designed to ensure high availability and data consistency across a cluster of nodes. The project provides a replicated key-value store and a coordination engine for managing distributed state. It distinguishes itself through support for multi-group consensus sharding to distribute traffic and a service provider interface that allows for custom log storage and entry encoding implementations. The system covers a wide range of distributed capabilities,

    Javaconsensusdistributed-consensus-algorithmsjava
    Auf GitHub ansehen↗3,806
  • oceanbase/oceanbaseAvatar von oceanbase

    oceanbase/oceanbase

    9,980Auf GitHub ansehen↗

    OceanBase is a distributed SQL database designed for high availability and strong consistency across multiple nodes and regions. It functions as a hybrid transactional and analytical processing engine, allowing real-time analytics and transactions to execute on a single data copy. The system also serves as a vector database engine for indexing and querying vector data to power semantic search and recommendation systems. The platform features native compatibility layers for MySQL and Oracle, enabling the migration of legacy workloads without rewriting SQL code. It utilizes a Paxos-based distri

    C++analyticscloud-nativedatabase
    Auf GitHub ansehen↗9,980
  • Alle 30 Alternativen zu Tikv anzeigen→