Softwr

Databases · head to head

Apache Pulsar vs etcd

Apache Pulsar logo

Apache Pulsar

Databases

Cloud-native messaging and streaming with separated storage

From
Free
Free plan
Yes
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

The short version

  • Apache Pulsar is free; etcd prices on request.
  • Only Apache Pulsar lists separated storage; only etcd lists raft consensus.
  • Where Apache Pulsar falls short: more components than Kafka: brokers, BookKeeper and ZooKeeper each need operating.
  • Prices and features on this page were last checked on 13 November 2026.

How do Apache Pulsar and etcd differ?

Apache Pulsar and etcd differ on starting price (Free against On request), pricing model and free tier (Yes against No). Only the attributes on which Apache Pulsar and etcd actually diverge.

Attributes where Apache Pulsar and etcd differ
AttributeApache Pulsaretcd
Starting priceFreeOn request
Pricing modelOpen source, no licence feeOpen-source
Free tierYesNo
PlatformsLinux, Self-hostedWeb

Identical on both: category (Databases).

Which features does each one have?

They share no listed features; 4 appear only for Apache Pulsar and 8 only for etcd. 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 Apache Pulsar

  • Separated storage
  • Queuing and streaming
  • Built-in multi-tenancy
  • Geo-replication

Only in etcd

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

What is each one used for?

Apache Pulsar is most often brought in for multi-tenant messaging where isolation between teams is a requirement; etcd for coordinating failover in a clustered database, as Patroni does for PostgreSQL. The jobs each tool is most often brought in to do.

Apache Pulsar

  • Platforms needing both work queues and replayable streams without running two systemsnot etcd
  • Multi-tenant messaging where isolation between teams is a requirementnot etcd
  • Deployments where storage and traffic grow at genuinely different ratesnot etcd

etcd

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

Where do Apache Pulsar and etcd fall short?

Apache Pulsar's most cited limit: more components than Kafka: brokers, BookKeeper and ZooKeeper each need operating. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Apache Pulsar

  • More components than Kafka: brokers, BookKeeper and ZooKeeper each need operating
  • Correspondingly harder to run well, and the expertise is rarer than Kafka expertise
  • A much smaller ecosystem of connectors, tooling and hiring pool than Kafka
  • The architectural advantages only pay off at a scale most deployments never reach

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

How much do Apache Pulsar and etcd cost?

Apache Pulsar is free to use. Plan by plan below, from each vendor's own pricing page.

Apache Pulsar

Free
  • Apache PulsarFree
    • Full functionality
    • No usage limits
    • Community support

etcd

On request

No published plan breakdown. See the etcd review.

Which should you pick?

Choose Apache Pulsar if

  • You need separated storage.
  • You want to start without paying.
  • You work on Linux, Self-hosted.
  • You also want queuing and streaming.

Choose etcd if

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

Questions people ask

Is Apache Pulsar or etcd better?
Neither clearly leads. Apache Pulsar starts at Free and etcd at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Apache Pulsar or etcd?
Apache Pulsar has a free tier; the other does not. Paid plans start at Free for Apache Pulsar and On request for etcd.
Does Apache Pulsar or etcd run on more platforms?
Apache Pulsar runs on Linux, Self-hosted. etcd runs on Web.
Can I use Apache Pulsar for free?
Yes. Apache Pulsar has a free tier, so you can try it without paying. etcd starts at On request.
What is Apache Pulsar best used for?
Apache Pulsar is most often used for platforms needing both work queues and replayable streams without running two systems, multi-tenant messaging where isolation between teams is a requirement, deployments where storage and traffic grow at genuinely different rates. Of those, platforms needing both work queues and replayable streams without running two systems and multi-tenant messaging where isolation between teams is a requirement are not what etcd is typically brought in for.
What can Apache Pulsar do that etcd cannot?
Apache Pulsar covers Separated storage, Queuing and streaming, Built-in multi-tenancy, Geo-replication. etcd covers Raft consensus, Linearizable reads, Transactions, Leases.

Answered from the vendors’ own pages

Apache Pulsar: Is Apache Pulsar free?

Yes, open source under the Apache Software Foundation.

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.

Apache Pulsar: Pulsar or Kafka?

Pulsar separates storage from compute and covers queuing and streaming in one system. Kafka has a far larger ecosystem and hiring pool. Most teams should have a specific reason before choosing Pulsar.

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.

Apache Pulsar: Why does separated storage matter?

Brokers hold no data, so adding or replacing one requires no rebalancing, and storage can grow without adding serving capacity.

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.

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.

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

Other head to heads