Databases · head to head
etcd vs SQLite

etcd
Databases
A distributed key-value store using Raft consensus, built for cluster coordination rather than application data.
- From
- On request
- Free plan
- No
SQLite
Databases
Small, fast, self-contained SQL database engine
- From
- Free
- Free plan
- Yes
The short version
- SQLite is a C-language library.
- SQLite is free; etcd prices on request.
- Only etcd lists raft consensus; only SQLite lists serverless Operation.
- Where SQLite falls short: supports only serialized write operations; only one process can modify the database at any moment, limiting concurrent users.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which etcd and SQLite actually diverge.
Identical on both: pricing model (Open-source), category (Databases).
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 SQLite
- Serverless Operation
- Zero Configuration
- Single File Database
- Cross-platform
- Full SQL Support
- ACID Compliance
- Self-contained
- Browser Storage
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 SQLite
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot SQLite
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot SQLite
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot SQLite
SQLite
- Transaction processingnot etcd
- Data storagenot etcd
- Application backendnot etcd
- Reportingnot etcd
- Data analyticsnot 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
SQLite
- Supports only serialized write operations; only one process can modify the database at any moment, limiting concurrent users
- No multi-user support or granular access control; relies on file system permissions for security only
- Limited ALTER TABLE functionality cannot edit or modify columns in existing tables
Pricing, plan by plan
etcd
On requestNo published plan breakdown. See the etcd review.
SQLite
Free- Public DomainFree
- Serverless
- Zero-configuration
- Cross-platform
Which should you pick?
Choose SQLite if
- You need serverless operation.
- You want to start without paying.
- You work on Linux, macOS, Windows, iOS, Android.
- You also want zero configuration.
Questions people ask
- Is etcd or SQLite better?
- Neither clearly leads. etcd starts at On request and SQLite at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, etcd or SQLite?
- SQLite has a free tier; the other does not. Paid plans start at On request for etcd and Free for SQLite.
- Does etcd or SQLite run on more platforms?
- etcd runs on Web. SQLite runs on Linux, macOS, Windows, iOS, Android.
- Can I use SQLite for free?
- Yes. SQLite 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 SQLite is typically brought in for.
- What can etcd do that SQLite cannot?
- etcd covers Raft consensus, Linearizable reads, Transactions, Leases. SQLite covers Serverless Operation, Zero Configuration, Single File Database, Cross-platform.
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.
SQLite: Is SQLite free and open source?
Yes, SQLite is open source and in the public domain. The complete source code and binaries are free to download and use for any purpose without restrictions.
Sourceetcd: 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.
SQLite: How does SQLite work and what is its design?
SQLite is a self-contained, serverless SQL database engine that reads and writes directly to disk files. It requires no separate server process and runs within your application, making it ideal for embedded systems and local storage.
Sourceetcd: 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.
SQLite: What are SQLite's limitations for scaling?
SQLite does not support true multi-user concurrency. Only one process can write to the database at a time, and it lacks user management and access control features. It is designed for small to medium projects, not enterprise applications with many concurrent users.
Sourceetcd: 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.
SQLite: Can I use SQLite for production web applications?
SQLite can work for single-server web applications with modest concurrency needs. However, it lacks features like user management, granular security, and sophisticated query optimization needed for large-scale applications.
Sourceetcd: 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
- 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 Postgres
- etcd vs Presto
- etcd vs Privacera
- etcd vs RavenDB
- etcd vs Readyset
- etcd vs Redpanda
- etcd vs Apache Airflow
- etcd vs DuckDB
- etcd vs PostgreSQL
- etcd vs MariaDB
- etcd vs Oracle Database
- etcd vs Cockroach Labs
- etcd vs Materialize
- etcd vs Microsoft SQL Server
- etcd vs DataGrip
- etcd vs Google Cloud SQL
- etcd vs IBM Db2
- etcd vs Chroma
- etcd vs Fivetran HVR
- etcd vs Grist
- etcd vs Instaclustr
- etcd vs LanceDB
- etcd vs Marqo
- SQLite vs DynamoDB
- SQLite vs Timeplus
- SQLite vs Firebase Realtime Database
- SQLite vs Knack
- SQLite vs Turso
- SQLite vs BigQuery
- SQLite vs TiDB
- SQLite vs Dgraph
- SQLite vs turbopuffer
- SQLite vs Apache Kafka
- SQLite vs Redis
- SQLite vs Postgres
- SQLite vs Presto
- SQLite vs Privacera
- SQLite vs RavenDB
- SQLite vs Readyset
- SQLite vs Redpanda
- SQLite vs Apache Airflow
- SQLite vs DuckDB
- SQLite vs PostgreSQL
- SQLite vs MariaDB
- SQLite vs Oracle Database
- SQLite vs Cockroach Labs
- SQLite vs Materialize
- SQLite vs Microsoft SQL Server
- SQLite vs DataGrip
- SQLite vs Google Cloud SQL
- SQLite vs IBM Db2
- SQLite vs Chroma
- SQLite vs Fivetran HVR
- SQLite vs Grist
- SQLite vs Instaclustr
- SQLite vs LanceDB
- SQLite vs Marqo
