E-Commerce · head to head
eBay vs etcd
eBay
E-Commerce
Global marketplace where sellers list into eBay's audience under eBay's fee schedule and rules
- From
- On request
- Free plan
- No

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
- Only eBay lists auction and fixed price listings; only etcd lists raft consensus.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which eBay and etcd actually diverge.
Identical on both: starting price (On request), free tier (No), platforms (Web).
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 eBay
- Auction and fixed price listings
- Managed payments
- eBay Stores
- Promoted Listings
- Bulk listing tools
- International selling programmes
- Money Back Guarantee
- Seller performance standards
Only in etcd
- Raft consensus
- Linearizable reads
- Transactions
- Leases
- Watches
- MVCC revision history
- Role-based access control
- Snapshot backup and restore
What people use each for
The jobs each tool is most often brought in to do.
eBay
- Selling used, refurbished or one-off stock that has no natural search demand on its own sitenot etcd
- Parts and spares catalogues where buyers search by fitment rather than by brandnot etcd
- Liquidating returns or excess inventory without building an audience for itnot etcd
- Testing whether demand exists for a product line before investing in a standalone storefrontnot etcd
etcd
- Storing Kubernetes cluster state, which is what the overwhelming majority of etcd deployments are doingnot eBay
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot eBay
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot eBay
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot eBay
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
eBay
- The final value fee applies to the total the buyer pays including postage and tax rather than to the item price, so a low value item with expensive shipping loses a much larger share of its margin than the headline percentage implies
- Fees stack rather than substitute, since a Store subscription, a per order fixed fee, Promoted Listings and cross-border percentages all apply on top of the category rate, and the effective take rate is only visible after a full month of settlement reports
- eBay controls search placement, so as a category gets competitive the practical cost of visibility becomes the Promoted Listings rate, and that is an auction against other sellers that only goes one way
- You do not get the customer relationship, because eBay mediates messaging and does not supply a marketing list, so repeat business depends on eBay showing your listing again rather than on anything you own
- The account is the entire asset and it is governed by policies eBay enforces unilaterally, so a suspension or a category restriction ends the revenue immediately with no portable equivalent of a domain, a theme or a customer database to move elsewhere
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
Pricing, plan by plan
eBay
On requestNo published plan breakdown. See the eBay review.
etcd
On requestNo published plan breakdown. See the etcd review.
Which should you pick?
Questions people ask
- Is eBay or etcd better?
- Neither clearly leads. eBay starts at On request and etcd at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, eBay or etcd?
- eBay starts at On request and etcd at On request.
- Does eBay or etcd run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- What is eBay best used for?
- eBay is most often used for selling used, refurbished or one-off stock that has no natural search demand on its own site, parts and spares catalogues where buyers search by fitment rather than by brand, liquidating returns or excess inventory without building an audience for it, testing whether demand exists for a product line before investing in a standalone storefront. Of those, selling used, refurbished or one-off stock that has no natural search demand on its own site and parts and spares catalogues where buyers search by fitment rather than by brand are not what etcd is typically brought in for.
- What can eBay do that etcd cannot?
- eBay covers Auction and fixed price listings, Managed payments, eBay Stores, Promoted Listings. etcd covers Raft consensus, Linearizable reads, Transactions, Leases.
Answered from the vendors’ own pages
eBay: What does selling on eBay actually cost?
A category-dependent percentage of the total buyer payment including postage, plus a fixed fee per order, plus any Store subscription, advertising rate and international fees. Model all of them together, not the first one alone.
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.
eBay: Can I use my own payment provider?
No. Payments run through eBay and settle to your bank account on eBay's payout schedule, so you do not choose the processor and you do not control settlement timing.
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.
eBay: Do I get my customers' email addresses?
Not for marketing. eBay mediates buyer contact, which is why sellers who rely on it have no list to fall back on if the channel changes.
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.
eBay: Is eBay an alternative to having my own store?
It is a channel, not a substitute. Sellers who use it well treat it as demand they rent while building something they own in parallel.
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.
Related pages
Other head to heads
- eBay vs Amazon Shopping
- eBay vs Gumroad
- eBay vs Mercari
- eBay vs Heartland Retail
- eBay vs Depop
- eBay vs Poshmark
- eBay vs Etsy
- eBay vs Wish
- eBay vs Vinted
- eBay vs NCR Voyix
- eBay vs Algopix
- eBay vs Namecheap
- eBay vs PrestaShop
- eBay vs Razorpay
- eBay vs Retail Pro
- eBay vs Saleor
- eBay vs SamCart
- eBay vs Sellfy
- eBay vs DynamoDB
- eBay vs Timeplus
- eBay vs Firebase Realtime Database
- eBay vs Knack
- eBay vs Turso
- eBay vs BigQuery
- eBay vs TiDB
- eBay vs Dgraph
- eBay vs turbopuffer
- eBay vs Apache Kafka
- eBay vs Redis
- eBay vs Fivetran HVR
- eBay vs Grist
- eBay vs IBM Db2
- eBay vs Instaclustr
- eBay vs LanceDB
- eBay vs Marqo
- eBay vs Apache Airflow
- etcd vs Amazon Shopping
- etcd vs Gumroad
- etcd vs Mercari
- etcd vs Heartland Retail
- etcd vs Depop
- etcd vs Poshmark
- etcd vs Etsy
- etcd vs Wish
- etcd vs Vinted
- etcd vs NCR Voyix
- etcd vs Algopix
- etcd vs Namecheap
- etcd vs PrestaShop
- etcd vs Razorpay
- etcd vs Retail Pro
- etcd vs Saleor
- etcd vs SamCart
- etcd vs Sellfy
- etcd vs DynamoDB
- etcd vs Timeplus
- etcd vs Firebase Realtime Database
- etcd vs Knack
- etcd vs Turso
- etcd vs BigQuery
- etcd vs TiDB
- etcd vs Dgraph
- etcd vs turbopuffer
- etcd vs Apache Kafka
- etcd vs Redis
- etcd vs Fivetran HVR
- etcd vs Grist
- etcd vs IBM Db2
- etcd vs Instaclustr
- etcd vs LanceDB
- etcd vs Marqo
- etcd vs Apache Airflow
