vs

etcd vs TiKV

etcd: Raft-based, strongly consistent key-value store that holds Kubernetes' cluster state. TiKV: CNCF-graduated, Raft-replicated transactional key-value store in Rust; the storage layer of TiDB.

key differences

  • TiKV is built for larger datasets (Multi-PB) than etcd (≤ 100 GB).
  • Horizontal scaling is none in etcd and native in TiKV.
  • Only etcd has pub/sub, role-based access.
  • Only TiKV has change data capture, compression, encryption at rest.

choose etcd for

  • +Kubernetes and control-plane state
  • +Service discovery and dynamic configuration
  • +Distributed locks and leader election
  • +Feature flags and small metadata for infrastructure

best at · Coordination, Metadata, Pub/Sub

choose tikv for

  • +Storage layer for distributed SQL (TiDB)
  • +Metadata for distributed file systems (JuiceFS)
  • +Large-scale transactional key-value services
  • +Redis-protocol or custom data layers needing strong consistency

best at · OLTP, Metadata, HTAP

overview
Primary model
Key-Value
Key-Value
Also supports
–
–
Type
Database engine
Database engine
Status
Active
Active
Developer
etcd maintainers / CNCF
PingCAP / CNCF
First release
2013
2016
Latest version
3.7.3 (Oct 22, 2026)
8.5.8 (Aug 27, 2026)
License
Open source (permissive)Apache License 2.0
Open source (permissive)Apache License 2.0
Free tier
✓
✓
popularity
WhichDB Score
32.4
20.8
Rank
#71
#148
GitHub stars
52.4K
16.9K
Stack Overflow questions
478
26
scale & guarantees
Comfortable data size
Small (≤ 100 GB)
Massive (Multi-PB)
Horizontal scaling
None
Native
Multi-region
None
Read replicas
ACID
Full
Full
Consistency
Strong
Strong
Schema
Schemaless
Schemaless
Architecture
Distributed, Client server
Distributed, Client server
deployment
Self-hosted
✓
✓
Vendor-managed cloud
—
—
Serverless
—
—
Embedded
—
—
Edge
—
—
Clouds
–
–
capabilities
Transactions
✓
✓
Joins
—
—
Secondary indexes
—
—
Full-text search
—
—
Vector search
—
—
Geospatial
—
—
JSON
—
—
Change data capture
—
✓
Triggers
—
—
Stored procedures
—
—
Materialized views
—
—
TTL / expiry
✓
✓
Pub/Sub
✓
—
Columnar storage
—
—
In-memory
—
—
Durable persistence
✓
✓
Compression
—
✓
Encryption at rest
—
✓
Role-based access
✓
—
Time travel
✓
✓
Branching
—
—
Online schema changes
—
—
Streaming ingest
—
—
Offline sync
—
—
Runs in WebAssembly
—
—
interfaces
Query languages
etcd v3 API
TiKV API (Raw and Transactional)
Client languages
Go, Java, Python, JavaScript, Rust, C++
Go, Rust, Java, Python, C++, JavaScript
Best for
Coordination, Metadata, Pub/Sub
OLTP, Metadata, HTAP

etcd vs TiKV: FAQ

What is the difference between etcd and TiKV?

etcd: Raft-based, strongly consistent key-value store that holds Kubernetes' cluster state. TiKV: CNCF-graduated, Raft-replicated transactional key-value store in Rust; the storage layer of TiDB. TiKV is built for larger datasets (Multi-PB) than etcd (≤ 100 GB). Horizontal scaling is none in etcd and native in TiKV. Only etcd has pub/sub, role-based access.

When should I choose etcd over TiKV?

Choose etcd for kubernetes and control-plane state; service discovery and dynamic configuration; and distributed locks and leader election. Choose TiKV for storage layer for distributed SQL (TiDB), metadata for distributed file systems (JuiceFS) and large-scale transactional key-value services.

Is etcd or TiKV more popular?

etcd ranks #71 on the WhichDB Score (32.4/100) and TiKV ranks #148 (20.8/100). Popularity is not fit: check the requirements that matter for your project.

Are etcd and TiKV open source?

Yes. etcd is open source. License: Apache License 2.0. Yes. TiKV is open source. License: Apache License 2.0.