Softwr

Databases · head to head

Dgraph vs etcd

Dgraph logo

Dgraph

Databases

Apache 2.0 distributed graph database written in Go, maintained by Hypermode, queried through GraphQL or its own DQL language.

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

  • Dgraph starts at $39/mo; etcd prices on request.
  • Only Dgraph lists apache 2.0 licence; only etcd lists linearizable reads.
  • Prices and features on this page were last checked on 13 November 2026.

How do Dgraph and etcd differ?

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

Attributes where Dgraph and etcd differ
AttributeDgraphetcd
Starting priceFreeOn request
Pricing modelFreemiumOpen-source
Free tierYesNo
PlatformsLinux, macOS, Self-hosted, WebWeb

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 Dgraph 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 Dgraph

  • Apache 2.0 licence
  • Generated GraphQL API
  • DQL query language
  • Predicate sharding
  • Raft replication
  • Distributed ACID transactions
  • Written in Go
  • Full-text and geo indexing

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.

Dgraph

  • An application whose core data is a graph, such as permissions, social connections or product relationships, where the frontend already consumes GraphQLnot etcd
  • A knowledge graph that outgrew a single machine and needs storage distributed across nodes without a per-core licence negotiationnot etcd
  • Recommendation or fraud-detection features that traverse several hops at request time, where a relational join chain has become the bottlenecknot etcd
  • Teams that want a graph database they can read, fork and self-host under a permissive licence rather than a source-available onenot etcd

etcd

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

Where do Dgraph and etcd fall short?

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

Dgraph

  • Sharding is by predicate, so a single very hot predicate lives entirely in one Raft group and cannot be split further; adding nodes does not relieve it and the fix is a data model change
  • Stewardship passed from Dgraph Labs to Hypermode after the original company stopped operating independently, so anyone building on it is betting on a second custodian rather than on the original team's roadmap
  • The GraphQL layer is generated and opinionated, so anything it does not express drops you into DQL, which is a second language your team must learn and which no other database speaks
  • The community is a fraction of Neo4j's, so operational answers, tuning experience, hiring and third-party tooling are all thinner, and unusual failure modes in a Zero and Alpha cluster leave you reading source rather than a forum
  • There is no portable graph standard to migrate to; Cypher, Gremlin and SPARQL are all different query models, so the schema and every query is a rewrite if you later leave, and that cost grows with the application

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

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

Dgraph

Free
  • CommunityFree
    • Native GraphQL
    • Graph queries
    • Full-text search
  • Cloud$39/mo
    • Managed service
    • Auto-scaling
    • Enterprise support

etcd

On request

No published plan breakdown. See the etcd review.

Which should you pick?

Choose Dgraph if

  • You need apache 2.0 licence.
  • You want to start without paying.
  • You work on Linux, macOS, Self-hosted, Web.
  • You also want generated graphql api.

Choose etcd if

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

Questions people ask

Is Dgraph or etcd better?
Neither clearly leads. Dgraph 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, Dgraph or etcd?
Dgraph has a free tier; the other does not. Paid plans start at Free for Dgraph and On request for etcd.
Does Dgraph or etcd run on more platforms?
Dgraph runs on Linux, macOS, Self-hosted, Web. etcd runs on Web.
Can I use Dgraph for free?
Yes. Dgraph has a free tier, so you can try it without paying. etcd starts at On request.
What is Dgraph best used for?
Dgraph is most often used for an application whose core data is a graph, such as permissions, social connections or product relationships, where the frontend already consumes graphql, a knowledge graph that outgrew a single machine and needs storage distributed across nodes without a per-core licence negotiation, recommendation or fraud-detection features that traverse several hops at request time, where a relational join chain has become the bottleneck, teams that want a graph database they can read, fork and self-host under a permissive licence rather than a source-available one. Of those, an application whose core data is a graph, such as permissions, social connections or product relationships, where the frontend already consumes graphql and a knowledge graph that outgrew a single machine and needs storage distributed across nodes without a per-core licence negotiation are not what etcd is typically brought in for.
What can Dgraph do that etcd cannot?
Dgraph covers Apache 2.0 licence, Generated GraphQL API, DQL query language, Predicate sharding. etcd covers Raft consensus, Linearizable reads, Transactions, Leases.

Answered from the vendors’ own pages

Dgraph: Is Dgraph open source?

Yes. The current repository is Apache 2.0, which is a permissive OSI licence, and the project is at v25 under Hypermode's maintenance.

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.

Dgraph: Is it really GraphQL?

It serves a generated GraphQL API, which is real GraphQL for clients. Its native language, DQL, resembles GraphQL syntactically but is Dgraph's own language and is not the GraphQL specification.

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.

Dgraph: How does it compare to Neo4j?

Neo4j has the larger ecosystem, Cypher, and far more operational precedent. Dgraph distributes storage across nodes by default and gives you a GraphQL endpoint without writing resolvers. The choice usually turns on whether you need horizontal scale and a GraphQL surface more than you need ecosystem depth.

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.

Dgraph: What does a production cluster look like?

At minimum a set of Zero nodes for coordination and a replicated set of Alpha nodes for data, typically three of each for fault tolerance, which is a meaningfully larger operational footprint than a single graph server.

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.

Dgraph: Who maintains it now?

Hypermode. Dgraph Labs, the original company, no longer operates it, and that change of custodian is the main non-technical risk to weigh.

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