Dgraph vs LatticeDB

Both are property graph databases. Dgraph (2015-12, Apache-2.0, Go) ranks #3 this month; LatticeDB (2026-01, MIT, Zig) ranks #114.

Attribute Dgraph #3 = Leader LatticeDB #114 new Growing
At a glance
Rank #3#114
Score 67.632.3
GitHub stars 21.8k646
Popularity 79.738.7
Activity 77.255.6
Community 67.387.6
Research 62.3
Fundamentals
Description A distributed graph database with horizontal scaling and ACID transactions. Uses its own query language (DQL) derived from GraphQL, with automatic shard rebalancing across cluster nodes.An embedded, single-file property graph database with vector similarity and BM25 full-text search in a shared query layer.
Vendor IstariJeff Hajewski
Model Property GraphProperty Graph
Kind databaseembedded
Category EnterpriseEmerging
First released 2015-122026-01
Status activeactive
License Apache-2.0MIT
Written in GoZig
Query languages DQL, GraphQLCypher
gdotv support yesno

Feature scores — not surveyed for LatticeDB

Feature DgraphLatticeDB
Community & Business
Active development
Commercial support
Live community 0.5
Open Source
Pricing ·
Trendiness 0.25
Deployment
Containerization
Work as dedicated instance
Work as embedded ·
Testing in-memory version
Platform
Operating on Linux
Operating on Windows
SaaS offering
Operations
Automatic updates ·
Client side caching ·
Data versioning support ·
Live backups
Distribution
Cluster Re-balancing
Data Distribution
High-Availability
Query Distribution
Replication support
Developer Experience
Data types defined
Logging/Auditing 0.5
Object-Graph Mapper ·
Reactive programming ·
Documentation up-to-date 0.5
Binary protocol
CLI ·
GUI
Data Model
Multi-database ·
Graph-native data
REST API
Query Language
Transactions
Granular locking ·
Multiple isolation levels ·
Read committed transaction ·
Transaction support
Schema & Security
Constraints ·
Schema support
Secondary indexes
Server side procedures ·
Triggers ·
Authentication
Authorization
Data encryption