DBMS > Dgraph vs. JaguarDB vs. Riak KV vs. XTDB

System Properties Comparison Dgraph vs. JaguarDB vs. Riak KV vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Performant, highly scalable DBMS for AI and IoT applications

Distributed, fault tolerant key-value store

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Graph DBMS

Key-value store
Vector DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Document store

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	1.39
Rank	#155	Overall
	#15	Graph DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores
	#16	Vector DBMS

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

dgraph.io

www.jaguardb.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

dgraph.io/docs

www.jaguardb.com/support.html

www.tiot.jp/riak-docs/riak/kv/latest

www.xtdb.com/docs

Developer

Dgraph Labs, Inc.

DataJaguar, Inc.

OpenSource, formerly Basho Technologies

Juxt Ltd.

Initial release

2016

2015

2009

2019

Current release

3.3 July 2023

3.2.0, December 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL V3.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

MIT License

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

the server part. Clients available in other languages

Erlang

Clojure

Server operating systems

Linux
OS X
Windows

Linux

Linux
OS X

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

limited SQL, making use of Apache Calcite

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JDBC
ODBC

HTTP API
Native Erlang Interface

HTTP REST
JDBC

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Clojure
Java

Server-side scripts

Stored procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication

selectable replication factor

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Planned for future releases

rights management via user accounts

yes, using Riak Security

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Dgraph on AWS: Setting up a horizontally scalable graph database
1 September 2020, AWS Blog

Dgraph raises $11.5 million for scalable graph database solutions
31 July 2019, VentureBeat

Graph Database Market size to grow by USD 7.40 billion between 2022 - 2027 | Growth Driven by Lack of standardization and programming flexibility - Technavio
13 December 2023, Yahoo Finance

Dgraph Rises to the Top Graph Database on GitHub With 11 G2 Badges and 11M Downloads
26 May 2021, Business Wire

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Top 8 Best NoSQL Databases in 2024
9 September 2024, AIM

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Basho aims for enterprise operational simplicity with new Data Platform
26 May 2015, diginomica

provided by Google News

Share this page