Softwr

Databases · head to head

etcd vs StarRocks

etcd logo

etcd

Databases

A distributed key-value store using Raft consensus, built for cluster coordination rather than application data.

From
On request
Free plan
No
Visit etcdFull review
StarRocks logo

StarRocks

Databases

Apache 2.0 MPP analytical database built for joins on open table formats

From
Free
Free plan
Yes
Visit StarRocksFull review

The short version

  • StarRocks is free; etcd prices on request.
  • Only etcd lists raft consensus; only StarRocks lists lakehouse query engine.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which etcd and StarRocks actually diverge.

Attributes where etcd and StarRocks differ
AttributeetcdStarRocks
Starting priceOn requestFree
Pricing modelOpen-sourceOpen source, no licence fee
Free tierNoYes
PlatformsWebLinux, Self-hosted

Identical on both: category (Databases).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in etcd

  • Raft consensus
  • Linearizable reads
  • Transactions
  • Leases
  • Watches
  • MVCC revision history
  • Role-based access control
  • Snapshot backup and restore

Only in StarRocks

  • Cost-based optimiser
  • Lakehouse query engine
  • Primary key tables
  • Materialised views
  • Shared-data mode
  • MySQL wire protocol

What people use each for

The jobs each tool is most often brought in to do.

etcd

  • Storing Kubernetes cluster state, which is what the overwhelming majority of etcd deployments are doingnot StarRocks
  • Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot StarRocks
  • Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot StarRocks
  • Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot StarRocks

StarRocks

  • Customer-facing analytics where queries join a fact table to several dimensions and must return in well under a secondnot etcd
  • Querying an Iceberg lakehouse directly without copying data into a proprietary warehouse formatnot etcd
  • Replacing a ClickHouse deployment that has become unmanageable because every new question needs another denormalised tablenot etcd
  • Real-time analytics fed by change data capture where rows must be updated in place rather than appendednot etcd

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

etcd

  • It is sized for coordination data, not application data: the default backend quota is 2 GB and 8 GB is the documented recommended maximum, and exceeding it puts the cluster into a NOSPACE alarm where it accepts no writes until an operator compacts, defragments and clears the alarm by hand
  • Every write is replicated and fsynced before acknowledgement, so cluster performance is bounded by the slowest disk in it; a member on network-attached storage with high fsync latency causes leader elections and cluster-wide latency spikes that look like network problems and are not
  • Adding members increases availability but reduces write throughput, because each write must reach a larger quorum; you run three or five members for fault tolerance, and increasing capacity means faster hardware rather than more nodes
  • There is no sharding and no multi-tenancy, so isolating workloads means running separate clusters, each with its own quorum, certificates, backup schedule and upgrade path, and that operational multiplication is often unexpected
  • Running it yourself is a real job: periodic compaction and defragmentation, snapshot backups you have actually rehearsed restoring, and rotation of both peer and client TLS certificates, none of which happens automatically outside a managed Kubernetes service
  • Losing quorum is not self-healing; recovering a cluster that has lost a majority means restoring from a snapshot and accepting that everything written since that snapshot is gone, which makes backup frequency a data-loss budget decision rather than a routine setting

StarRocks

  • Self-hosting is a genuine operations job: frontend and backend node roles, tablet distribution, compaction and materialised view refresh all need an owner, and there is no small-team-friendly single-binary mode
  • CelerData is by far the dominant contributor despite Linux Foundation stewardship, so the practical roadmap risk is the same as any single-vendor open source project
  • It inherits a MySQL-flavoured SQL dialect from its Doris ancestry, so queries written for PostgreSQL, Snowflake or Trino need rewriting rather than porting
  • Ecosystem support is thinner than ClickHouse or Trino: fewer client libraries, fewer managed hosting options and a much smaller pool of engineers who have run it in production
  • Memory pressure under concurrent large joins is a common production failure, and the tuning knobs for query memory limits are unforgiving compared with a cloud warehouse that just scales

Pricing, plan by plan

etcd

On request

No published plan breakdown. See the etcd review.

StarRocks

Free
  • StarRocksFree
    • Apache 2.0 licence
    • Linux Foundation governance
    • No usage or node limits
  • CelerData CloudOn request
    • Managed StarRocks from the primary contributor
    • BYOC and serverless deployment options
    • Enterprise support and SLAs

Which should you pick?

Choose etcd if

  • You need raft consensus.
  • You also want linearizable reads.
etcd review

Choose StarRocks if

  • You need cost-based optimiser.
  • You want to start without paying.
  • You work on Linux, Self-hosted.
  • You also want lakehouse query engine.
StarRocks review

Questions people ask

Is etcd or StarRocks better?
Neither clearly leads. etcd starts at On request and StarRocks at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, etcd or StarRocks?
StarRocks has a free tier; the other does not. Paid plans start at On request for etcd and Free for StarRocks.
Does etcd or StarRocks run on more platforms?
etcd runs on Web. StarRocks runs on Linux, Self-hosted.
Can I use StarRocks for free?
Yes. StarRocks has a free tier, so you can try it without paying. etcd starts at On request.
What is etcd best used for?
etcd is most often used for storing kubernetes cluster state, which is what the overwhelming majority of etcd deployments are doing, leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactions, service discovery and dynamic configuration where readers need to be notified of changes rather than poll for them, coordinating failover in a clustered database, as patroni does for postgresql. Of those, storing kubernetes cluster state, which is what the overwhelming majority of etcd deployments are doing and leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactions are not what StarRocks is typically brought in for.
What can etcd do that StarRocks cannot?
etcd covers Raft consensus, Linearizable reads, Transactions, Leases. StarRocks covers Cost-based optimiser, Lakehouse query engine, Primary key tables, Materialised views.

Answered from the vendors’ own pages

etcd: Can I use etcd as an application database?

No. It is designed for metadata and coordination, with a recommended maximum store size of around 8 GB, no sharding and a write path deliberately optimised for durability rather than throughput. Application data belongs in a database built for it.

StarRocks: Is StarRocks open source?

Yes, Apache 2.0, governed under the Linux Foundation since 2023.

etcd: How many members should a cluster have?

Three for most cases, five where you need to survive two simultaneous failures. Always an odd number, because an even-sized cluster gains no additional fault tolerance while making quorum harder to reach.

StarRocks: How does it differ from ClickHouse?

StarRocks is built for joins across a star schema with a cost-based optimiser; ClickHouse is fastest on denormalised single tables.

etcd: What happens when the store fills up?

The cluster raises a NOSPACE alarm and stops accepting writes, becoming effectively read-only. Recovery requires compacting old revisions, defragmenting each member and then explicitly disarming the alarm, all done by an operator.

StarRocks: Who maintains it?

CelerData, formerly StarRocks Inc, is the dominant contributor and sells the managed service.

etcd: Why is my etcd cluster slow or unstable?

Almost always disk latency. Because every write is fsynced before acknowledgement, slow or shared storage causes heartbeat timeouts, leader elections and cascading latency. Local SSDs with low fsync latency are effectively a requirement.

StarRocks: Can it query Iceberg tables directly?

Yes, along with Hudi, Delta Lake, Hive and Paimon, with a local cache for repeat queries.

etcd: How does it compare with Consul or ZooKeeper?

All three provide consensus-backed coordination. etcd has the simplest data model and the Kubernetes ecosystem behind it; Consul bundles service discovery, health checking and a service mesh; ZooKeeper is older, JVM-based and still common under Kafka and Hadoop-era systems.

Share

Related pages

More on etcd

More on StarRocks

Keep looking

Other head to heads