Softwr

Databases · head to head

etcd vs Vendure

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

Vendure

E-Commerce

Modern headless GraphQL commerce framework

From
On request
Free plan
No

The short version

  • Vendure is a headless commerce framework.
  • Only etcd lists raft consensus; only Vendure lists GraphQL API.
  • Where Vendure falls short: pricing is custom-quoted per project with no published tiers or starting price.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which etcd and Vendure actually diverge.

Attributes where etcd and Vendure differ
AttributeetcdVendure
Pricing modelOpen-sourceQuote
PlatformsWebSelf-hosted, Web
CategoryDatabasesE-Commerce

Identical on both: starting price (On request), free tier (No).

Not yet recorded: founded for etcd.

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 Vendure

  • GraphQL API
  • TypeScript native
  • Plugin architecture
  • Admin UI
  • Multi-channel
  • Asset management
  • Order workflow
  • Faceted search

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

Vendure

  • B2B complex commerce workflowsnot etcd
  • Multi-brand and multi-currency operationsnot etcd
  • Custom pricing and contract managementnot 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

Vendure

  • Pricing is custom-quoted per project with no published tiers or starting price
  • Requires implementation partner or in-house development; no low-code or no-code option
  • GPLv3 free tier (Vendure Core) has different licensing than commercial product

Pricing, plan by plan

etcd

On request

No published plan breakdown. See the etcd review.

Vendure

On request
  • Platform (Self-hosted)On request
    • Flat annual subscription
    • No GMV, order, user, or capability-based charges
    • Complete Platform feature set
  • Vendure CloudOn request
    • Managed platform option
    • Same Platform feature set as self-hosted
    • Pricing not specified on website

Which should you pick?

Choose etcd if

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

Choose Vendure if

  • You need graphql api.
  • You work on Self-hosted, Web.
  • You also want typescript native.

Questions people ask

Is etcd or Vendure better?
Neither clearly leads. etcd starts at On request and Vendure at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, etcd or Vendure?
etcd starts at On request and Vendure at On request.
Does etcd or Vendure run on more platforms?
etcd runs on Web. Vendure runs on Self-hosted, Web.
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 Vendure is typically brought in for.
What can etcd do that Vendure cannot?
etcd covers Raft consensus, Linearizable reads, Transactions, Leases. Vendure covers GraphQL API, TypeScript native, Plugin architecture, Admin UI.

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.

Vendure: How is Vendure priced?

Vendure uses flat annual pricing with no charges based on GMV, order volume, user count, or specific capabilities. Pricing is quoted individually per project based on business requirements.

Source
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.

Vendure: Does Vendure charge for the runtime?

No additional fee is required for the Vendure runtime. Organizations can deploy it on their own infrastructure at no extra cost beyond the platform subscription.

Source
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.

Vendure: What is included in Vendure's subscription?

The annual platform subscription includes B2B storefront capabilities, pricing engines, catalogs, search, integrations, operations, brands/markets management, platform support, security updates, quarterly roadmap calls, and commercial licensing with IP indemnification.

Source
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