Open Source Alternatives LogoOpen Source Alternatives
AlternativesBlogAdvertise
Open Source Alternatives LogoOpen Source Alternatives

Stay Updated

Subscribe to our newsletter for the latest news and updates about Alternatives

Open Source Alternatives LogoOpen Source Alternatives

Handpicked Open Source Alternatives to Paid Softwares

Product
  • Search
  • Categories
  • Tag
  • Sign In
Resources
  • Blog
  • Collection
  • Submit
  • Advertise your tool
Company
  • Privacy Policy
  • Terms of Service
  • Refund Policy
  • Sitemap
Copyright © 2026 All Rights Reserved.
Home/Categories/Databases & Storage/TiKV
icon of TiKV

TiKV

Open source alternative to Amazon DynamoDB, Azure Cosmos DB and Google Cloud Firestore (in Datastore mode)

It is a highly scalable, low-latency, distributed key-value database designed for building robust data storage solutions.

image of TiKV
Contents
  1. 01Who TiKV is for

Repository

Stars
16.7K
Forks
2.3K
License
Apache-2.0
Latest
v8.5.6
Last commit
19 days ago
Last verified
May 13, 2026
Repo
tikv/tikv ↗

Additional details

16.7K starsRustApache-2.0Active this month
Visit websiteGitHub repo
  • 02The problem it solves
  • 03How it solves it
  • 04Strengths and trade-offs
  • 05TiKV vs alternatives
  • 06Tech stack
  • 07FAQ
  • 08Similar open-source tools
    • TL;DR

    TiKV is an Apache-2.0 distributed transactional key-value database built with Rust and the Raft consensus algorithm. It replaces single-node key-value stores when infrastructure teams need horizontal scale, strong consistency, and a storage layer used by TiDB.Apache-2.0 · Rust · 16.7K stars · Active this month

    who it's for

    Who TiKV is for#

    Infrastructure teams building distributed databases

    Use TiKV when you need a consistent key-value storage layer and have the expertise to operate distributed systems.

    Skip if:

    Skip if you need a turnkey SQL database for application developers.

    Teams evaluating TiDB storage internals

    TiKV helps platform engineers understand and tune the storage layer behind TiDB workloads.

    Skip if:

    Skip if your database problem can be solved with a managed relational service.

    the problem

    The problem it solves#

    how TiKV solves it

    How it solves it#

    Distributed key-value storage

    Splits data across nodes and regions so storage can scale horizontally instead of depending on one server.

    Raft-based replication

    Uses Raft consensus for replicated data and strong consistency across failures.

    Transactional API foundation

    Provides a transactional key-value layer used by TiDB and useful for systems that need consistent distributed storage.

    strengths · trade-offs

    Strengths and trade-offs#

    Strengths

    • Battle-tested inside TiDBTiKV is not only a research project; it serves as the storage layer for TiDB deployments.
    • Apache-2.0 Rust codebaseThe permissive license and Rust implementation make TiKV attractive for infrastructure teams evaluating distributed storage internals.

    Trade-offs

    • -Not an application database by itselfMost product teams should use TiDB or another higher-level database. TiKV is an infrastructure component that requires distributed systems skill to operate directly.
    versus alternatives

    TiKV vs alternatives#

    tech stack · detected from GitHub

    What it's built on#

    Languages
    PerlPythonRust
    Infrastructure
    AWS
    frequently asked

    FAQ#

    Is TiKV open source?

    Yes. TiKV is open source under the Apache-2.0 license.

    What is TiKV used for?

    TiKV is used as a distributed transactional key-value store and as the storage layer for TiDB.

    How does TiKV compare to DynamoDB?
    also worth a look

    Similar open-source tools#

    Apache CouchDB

    Apache CouchDB

    NoSQL database with multi-primary sync and HTTP API

    6.9KErlangApache-2.0
    MongoDB

    MongoDB

    Popular open source NoSQL document database for modern apps

    28.3KC++
    OrientDB

    OrientDB

    Multi-model NoSQL database: graphs, docs, and key-value

    5KJavaApache-2.0
    JanusGraph

    JanusGraph

    Distributed open source graph database for massive scale

    5.8KJavaApache-2.0
    ArangoDB

    ArangoDB

    Multi-model database: documents, graphs, and key-value in one

    14.2KC++
    RethinkDB

    RethinkDB

    Open source distributed document database with real-time feeds

    27KC++Apache-2.0
    Language
    Rust
    Open issues
    1,727
    Contributors
    475
    First release
    2015

    Categories

    Databases & StorageData & AnalyticsDeveloper Tools

    Tags

    DatabaseCloud NativeDeveloper ToolsMonitoringOpen CoreKubernetesAPI Infrastructure

    Single-node key-value stores are simple, but they become risky when data must survive node failures, scale horizontally, and keep strong consistency. Teams can shard manually or depend on a managed cloud database, but both choices add operational or vendor constraints.

    Distributed transactional storage is hard because replication, consensus, rebalancing, and failure recovery must work together. Teams need a storage engine that already solves those distributed systems problems.

    TiKV vs DynamoDB

    TiKV and DynamoDB both address scalable key-value storage, but they target different operators. TiKV is an open source distributed storage engine; DynamoDB is a fully managed AWS database product.

    TiKV is better for infrastructure teams that need control over a strongly consistent storage layer. DynamoDB is still better when the team wants AWS to own operations, scaling, and availability.

    DynamoDB is a managed AWS key-value and document database. TiKV is an open source distributed storage engine that teams operate themselves or use through TiDB.