Softwr

Databases · head to head

etcd vs RisingWave

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
RisingWave logo

RisingWave

Databases

Streaming database that maintains incremental materialised views in SQL instead of Flink jobs

From
Free
Free plan
Yes
Visit RisingWaveFull review

The short version

  • RisingWave starts at $0.227/mo; etcd prices on request.
  • Only etcd lists raft consensus; only RisingWave lists SQL materialised views.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which etcd and RisingWave actually diverge.

Attributes where etcd and RisingWave differ
AttributeetcdRisingWave
Starting priceOn requestFree
Pricing modelOpen-sourcePer RisingWave Unit hour
Free tierNoYes
PlatformsWebLinux, Self-hosted, Web

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 RisingWave

  • SQL materialised views
  • Postgres wire compatibility
  • Object storage state
  • Source connectors
  • Sink connectors
  • Iceberg tables
  • Watermarks and windowing
  • User defined functions

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 RisingWave
  • Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot RisingWave
  • Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot RisingWave
  • Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot RisingWave

RisingWave

  • A team with Kafka topics that needs continuously fresh aggregates for a dashboard without standing up a Flink clusternot etcd
  • A fraud or risk team maintaining rolling counters and joins across event streams expressed as SQL viewsnot etcd
  • A company doing Postgres CDC into a real-time denormalised view for search or servingnot etcd
  • An analytics group that wants streaming results landed directly into Apache Iceberg without a separate writer jobnot 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

RisingWave

  • Anything that does not fit SQL, such as custom windowing, complex event processing or heavy stateful logic, still needs Flink, so RisingWave often adds a system rather than removing one
  • The Apache 2.0 community edition excludes premium features behind a licence key, and which capabilities sit on which side of that line moves between releases, so a self-hosted plan can be invalidated by an upgrade
  • Long-running materialised views accumulate state in object storage, and cost and recovery time grow with retention in ways that are hard to forecast before you are in production
  • The Postgres compatibility is protocol level; it is not a transactional Postgres and using it as a general purpose database, with point updates or high write concurrency, goes badly
  • It is a comparatively young venture-funded project competing with Flink, Materialize and warehouse-native streaming, and the ecosystem of connectors, operators and third-party expertise is much thinner

Pricing, plan by plan

etcd

On request

No published plan breakdown. See the etcd review.

RisingWave

Free
  • Community EditionFree
    • Apache 2.0 licence, self-hosted
    • Core streaming engine and connectors
    • Premium features excluded and require a licence key
  • Cloud Basic$0.227/hour
    • Billed per RisingWave Unit hour
    • Hosted on AWS, GCP or Azure
    • Capped at 64 cores
  • Cloud ProOn request
    • No core limit
    • Bring your own cloud option
    • Premium features included
  • Self-managed EnterpriseOn request
    • On premises or Kubernetes
    • Premium features unlocked by licence
    • Annual contract with SLA

Which should you pick?

Choose etcd if

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

Choose RisingWave if

  • You need sql materialised views.
  • You want to start without paying.
  • You work on Linux, Self-hosted, Web.
  • You also want postgres wire compatibility.
RisingWave review

Questions people ask

Is etcd or RisingWave better?
Neither clearly leads. etcd starts at On request and RisingWave at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, etcd or RisingWave?
RisingWave has a free tier; the other does not. Paid plans start at On request for etcd and Free for RisingWave.
Does etcd or RisingWave run on more platforms?
etcd runs on Web. RisingWave runs on Linux, Self-hosted, Web.
Can I use RisingWave for free?
Yes. RisingWave 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 RisingWave is typically brought in for.
What can etcd do that RisingWave cannot?
etcd covers Raft consensus, Linearizable reads, Transactions, Leases. RisingWave covers SQL materialised views, Postgres wire compatibility, Object storage state, Source connectors.

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.

RisingWave: Is RisingWave open source?

The community edition is Apache 2.0 and self-hostable, but a set of premium features requires a paid licence key.

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.

RisingWave: What does the cloud cost?

It starts at 0.227 US dollars per RisingWave Unit hour on the Basic tier, which is capped at 64 cores.

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.

RisingWave: Does it replace Flink?

For SQL-expressible transformations, often yes. For custom stateful processing and complex event handling, no.

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.

RisingWave: Can I query it like Postgres?

Yes over the Postgres wire protocol, but it is an analytical streaming engine, not a transactional database.

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 RisingWave

Keep looking

Other head to heads