vs

etcd vs Consul KV

etcd: Raft-based, strongly consistent key-value store that holds Kubernetes' cluster state. Consul KV: The key-value store built into HashiCorp Consul for service config, locks and discovery.

key differences

  • Licensing: etcd is open source (permissive) (Apache License 2.0); Consul KV is source-available (Business Source License 1.1).
  • Transactions: etcd offers full ACID; Consul KV offers limited.
  • Only etcd has ttl / expiry, time travel.

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 hashicorp-consul-kv for

  • +Dynamic configuration for services in a Consul mesh
  • +Feature flags rendered via consul-template
  • +Distributed locks and leader election

best at · Coordination, Metadata

overview
Primary model
Key-Value
Key-Value
Also supports
–
–
Type
Database engine
Database engine
Status
Active
Active
Developer
etcd maintainers / CNCF
HashiCorp (IBM)
First release
2013
2014
Latest version
3.7.3 (Oct 22, 2026)
2.1.0 (Oct 22, 2026)
License
Open source (permissive)Apache License 2.0
Source-availableBusiness Source License 1.1
Free tier
✓
✓
popularity
WhichDB Score
32.4
39.0
Rank
#71
#49
GitHub stars
52.4K
30.1K
Stack Overflow questions
478
1.1K
scale & guarantees
Comfortable data size
Small (≤ 100 GB)
Small (≤ 100 GB)
Horizontal scaling
None
None
Multi-region
None
None
ACID
Full
Limited
Consistency
Strong
Strong, Eventual
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
Consul HTTP API
Client languages
Go, Java, Python, JavaScript, Rust, C++
Go, Python, Java, JavaScript, C#, Ruby
Best for
Coordination, Metadata, Pub/Sub
Coordination, Metadata

etcd vs Consul KV: FAQ

What is the difference between etcd and Consul KV?

etcd: Raft-based, strongly consistent key-value store that holds Kubernetes' cluster state. Consul KV: The key-value store built into HashiCorp Consul for service config, locks and discovery. Licensing: etcd is open source (permissive) (Apache License 2.0); Consul KV is source-available (Business Source License 1.1). Transactions: etcd offers full ACID; Consul KV offers limited. Only etcd has ttl / expiry, time travel.

When should I choose etcd over Consul KV?

Choose etcd for kubernetes and control-plane state; service discovery and dynamic configuration; and distributed locks and leader election. Choose Consul KV for dynamic configuration for services in a Consul mesh; feature flags rendered via consul-template; and distributed locks and leader election.

Is etcd or Consul KV more popular?

Consul KV ranks #49 on the WhichDB Score (39.0/100) and etcd ranks #71 (32.4/100). Popularity is not fit: check the requirements that matter for your project.

Are etcd and Consul KV open source?

Yes. etcd is open source. License: Apache License 2.0. Not in the OSI sense. Consul KV is source-available: you can read the code, but the license restricts some uses, typically offering it as a competing managed service. License: Business Source License 1.1.