DBMS > Dgraph vs. LeanXcale vs. Riak KV vs. Transbase

System Properties Comparison Dgraph vs. LeanXcale vs. Riak KV vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Distributed, fault tolerant key-value store

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Graph DBMS

Key-value store
Relational DBMS

Key-value store

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

Relational DBMS

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

dgraph.io

www.leanxcale.com

www.transaction.de/en/products/transbase.html

Technical documentation

dgraph.io/docs

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

www.transaction.de/en/products/transbase/features.html

Developer

Dgraph Labs, Inc.

LeanXcale

OpenSource, formerly Basho Technologies

Transaction Software GmbH

Initial release

2016

2015

2009

1987

Current release

3.2.0, December 2022

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache version 2, commercial enterprise edition

commercial

free development 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

Erlang

C and C++

Server operating systems

Linux
OS X
Windows

Linux
OS X

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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

yes

through Apache Derby

yes

APIs and other access methods

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

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

HTTP API
Native Erlang Interface

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

C
Java
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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

Erlang

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

selectable replication factor

Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

User concepts

Access control

Planned for future releases

yes, using Riak Security

fine grained access rights according to SQL-standard

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 | Amazon Web Services
1 September 2020, AWS Blog

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

Dgraph Raises $6M in Seed Funding
20 July 2022, FinSMEs

Dgraph GraphQL database users detail graph use cases
20 April 2021, TechTarget

provided by Google News

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

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

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

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

Basho distributes Riak to more customers - DCD
28 November 2013, DatacenterDynamics

provided by Google News

Share this page