Softwr

Databases · head to head

BigQuery vs etcd

BigQuery logo

BigQuery

Databases

Google Cloud's serverless analytical warehouse, billed either by bytes scanned per query or by reserved compute slots.

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

  • BigQuery starts at $6.25/mo; etcd prices on request.
  • Only BigQuery lists serverless compute; only etcd lists raft consensus.
  • Prices and features on this page were last checked on 13 November 2026.

How do BigQuery and etcd differ?

BigQuery and etcd differ on starting price (Free against On request), pricing model (Usage-based against Open-source) and free tier (Yes against No). Only the attributes on which BigQuery and etcd actually diverge.

Attributes where BigQuery and etcd differ
AttributeBigQueryetcd
Starting priceFreeOn request
Pricing modelUsage-basedOpen-source
Free tierYesNo
PlatformsWeb, APIWeb

Identical on both: category (Databases).

Not yet recorded: founded for etcd.

Which features does each one have?

They share no listed features; 10 appear only for BigQuery 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 BigQuery

  • Serverless compute
  • Separation of storage and compute
  • Two pricing models
  • Partitioning and clustering
  • Materialised views
  • BigQuery ML
  • Storage Write API
  • BI Engine

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?

etcd is most often brought in for coordinating failover in a clustered database, as Patroni does for PostgreSQL. The jobs each tool is most often brought in to do.

BigQuery

  • A warehouse for an organisation already on Google Cloud, where identity, logging and billing are consolidated in the same placenot etcd
  • Bursty analytical workloads with long idle periods, where paying per query beats keeping a cluster runningnot etcd
  • Event and clickstream analytics ingested continuously through the Storage Write API and queried without a load windownot etcd
  • Analytics teams with no infrastructure staff, where the absence of anything to tune or patch is worth more than dialect portabilitynot etcd

etcd

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

Where do BigQuery and etcd fall short?

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

BigQuery

  • On-demand billing charges for bytes read from every column a query references, so an unqualified select or a missing partition filter turns a routine query into a large bill, and the cost is discovered after the fact rather than at review time
  • There is no way to join tables that live in different regions, so a data estate split across regions for residency reasons has to be reconciled with copies and the storage and transfer that implies
  • It is not built for point lookups; retrieving a single row has latency measured in hundreds of milliseconds or more, so BigQuery cannot serve an application's read path and always needs a second store in front of it
  • Frequent small mutations run into DML concurrency limits and the cost of rewriting storage blocks, so a workload that updates individual rows continuously behaves badly compared with an append-only design
  • The compute exists only inside Google Cloud, so while tables can be exported, the accumulated GoogleSQL, scheduled queries, authorised views, ML models and IAM structure do not move, and switching warehouses is a rewrite of the analytical layer

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 BigQuery and etcd cost?

BigQuery has a free plan, with paid plans from $6.25/mo. Plan by plan below, from each vendor's own pricing page.

BigQuery

Free
  • Free TierFree
    • 1TB queries/month
    • 10GB storage/month
    • Standard support
  • On-demand$6.25/tb
    • Pay per query
    • Pay per storage
    • All features

etcd

On request

No published plan breakdown. See the etcd review.

Which should you pick?

Choose BigQuery if

  • You need serverless compute.
  • You want to start without paying.
  • You work on Web, API.
  • You also want separation of storage and compute.

Choose etcd if

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

Questions people ask

Is BigQuery or etcd better?
Neither clearly leads. BigQuery 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, BigQuery or etcd?
BigQuery has a free tier; the other does not. Paid plans start at Free for BigQuery and On request for etcd.
Does BigQuery or etcd run on more platforms?
BigQuery runs on Web, API. etcd runs on Web.
Can I use BigQuery for free?
Yes. BigQuery has a free tier, so you can try it without paying. etcd starts at On request.
What is BigQuery best used for?
BigQuery is most often used for a warehouse for an organisation already on google cloud, where identity, logging and billing are consolidated in the same place, bursty analytical workloads with long idle periods, where paying per query beats keeping a cluster running, event and clickstream analytics ingested continuously through the storage write api and queried without a load window, analytics teams with no infrastructure staff, where the absence of anything to tune or patch is worth more than dialect portability. Of those, a warehouse for an organisation already on google cloud, where identity, logging and billing are consolidated in the same place and bursty analytical workloads with long idle periods, where paying per query beats keeping a cluster running are not what etcd is typically brought in for.
What can BigQuery do that etcd cannot?
BigQuery covers Serverless compute, Separation of storage and compute, Two pricing models, Partitioning and clustering. etcd covers Raft consensus, Linearizable reads, Transactions, Leases.

Answered from the vendors’ own pages

BigQuery: How is BigQuery actually billed?

Storage is billed separately from compute. Compute is either on-demand, priced by the bytes a query reads from the referenced columns, or capacity-based, where you reserve autoscaling slots. Most cost surprises come from on-demand queries that scan more than expected.

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.

BigQuery: How do I control query cost?

Partition and cluster tables so queries prune data, select only the columns needed, use materialised views for repeated aggregations, and set maximum bytes billed on queries so a runaway scan fails instead of billing.

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.

BigQuery: Can I use it without being on Google Cloud?

The service only runs on Google Cloud. BigQuery Omni can query data held in S3 or Azure storage, but the compute is still Google's and the account relationship is still with Google.

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.

BigQuery: Is it suitable for serving application queries?

No. Latency for single-row reads is far too high. BigQuery is an analytical warehouse and application read paths need a transactional database or a cache in front of it.

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.

BigQuery: When should I move from on-demand to capacity pricing?

When on-demand spend becomes both large and predictable, or when unpredictable spend is a bigger problem than query queueing. The switch trades a variable bill for a fixed one plus contention between workloads.

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