Softwr

Databases · head to head

etcd vs Google Cloud SQL

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
Google Cloud SQL logo

Google Cloud SQL

Databases

Fully managed relational database service for MySQL, PostgreSQL, and SQL Server

From
Free
Free plan
Yes

The short version

  • Google Cloud SQL starts at $25/mo; etcd prices on request.
  • Only etcd lists raft consensus; only Google Cloud SQL lists high Availability.
  • Where Google Cloud SQL falls short: locked into Google Cloud ecosystem with limited cross-cloud portability.
  • Prices and features on this page were last checked on 13 November 2026.

How do etcd and Google Cloud SQL differ?

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

Attributes where etcd and Google Cloud SQL differ
AttributeetcdGoogle Cloud SQL
Starting priceOn requestFree
Pricing modelOpen-sourceUsage-based
Free tierNoYes

Identical on both: platforms (Web), category (Databases).

Not yet recorded: founded for etcd.

Which features does each one have?

They share no listed features; 8 appear only for etcd and 14 only for Google Cloud SQL. 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 Google Cloud SQL

  • High Availability
  • Automated Backups
  • Point-in-time Recovery
  • Encryption
  • Regional/Zonal Instances
  • Read Replicas
  • Private IP
  • BigQuery

What is each one used for?

etcd is most often brought in for coordinating failover in a clustered database, as Patroni does for PostgreSQL; Google Cloud SQL for transaction processing. 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 Google Cloud SQL
  • Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot Google Cloud SQL
  • Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot Google Cloud SQL
  • Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot Google Cloud SQL

Google Cloud SQL

  • Transaction processingnot etcd
  • Data storagenot etcd
  • Application backendnot etcd
  • Reportingnot etcd
  • Data analyticsnot etcd

Where do etcd and Google Cloud SQL fall short?

Google Cloud SQL's most cited limit: locked into Google Cloud ecosystem with limited cross-cloud portability. 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

Google Cloud SQL

  • Locked into Google Cloud ecosystem with limited cross-cloud portability
  • Pay-as-you-go pricing can become expensive with unpredictable workloads
  • Limited customization options compared to self-managed databases

How much do etcd and Google Cloud SQL cost?

Google Cloud SQL has a free plan, with paid plans from $25/mo. Plan by plan below, from each vendor's own pricing page.

etcd

On request

No published plan breakdown. See the etcd review.

Google Cloud SQL

Free
  • Free TierFree
    • db-f1-micro instance
    • 30GB storage
    • Limited usage
  • Standard$25/mo
    • High availability
    • Automated backups
    • Point-in-time recovery

Which should you pick?

Choose etcd if

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

Choose Google Cloud SQL if

  • You need high availability.
  • You want to start without paying.
  • You also want automated backups.

Questions people ask

Is etcd or Google Cloud SQL better?
Neither clearly leads. etcd starts at On request and Google Cloud SQL at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, etcd or Google Cloud SQL?
Google Cloud SQL has a free tier; the other does not. Paid plans start at On request for etcd and Free for Google Cloud SQL.
Does etcd or Google Cloud SQL run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use Google Cloud SQL for free?
Yes. Google Cloud SQL 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 Google Cloud SQL is typically brought in for.
What can etcd do that Google Cloud SQL cannot?
etcd covers Raft consensus, Linearizable reads, Transactions, Leases. Google Cloud SQL covers High Availability, Automated Backups, Point-in-time Recovery, Encryption.

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.

Google Cloud SQL: What database engines does Google Cloud SQL support?

Google Cloud SQL supports MySQL, PostgreSQL, and SQL Server. Users can choose their preferred engine when provisioning an instance and Google handles automated backups, replication, patching, and scaling.

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.

Google Cloud SQL: Does Google Cloud SQL have a free tier?

Google Cloud SQL does not have a free tier, though new users receive free trial credits from Google Cloud Platform. Pricing is based on compute resources (CPU and memory) and storage used, with options for committed use discounts.

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.

Google Cloud SQL: Can Google Cloud SQL scale automatically?

Yes. Cloud SQL automatically scales database storage and compute resources to handle increased workloads without manual intervention, and includes automated backups and high availability configurations.

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