DBMS > LMDB vs. Riak KV vs. SAP HANA vs. TigerGraph vs. TinkerGraph

System Properties Comparison LMDB vs. Riak KV vs. SAP HANA vs. TigerGraph vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

A high performant, light-weight, embedded key-value database library

Distributed, fault tolerant key-value store

In-memory, column based data store. Available as appliance or cloud service

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Key-value store

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

Relational DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.99
Rank	#125	Overall
	#21	Key-value stores

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

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

www.symas.com/symas-embedded-database-lmdb

www.sap.com/products/hana.html

www.tigergraph.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

www.lmdb.tech/doc

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

help.sap.com/hana

docs.tigergraph.com

Developer

Symas

OpenSource, formerly Basho Technologies

SAP

Initial release

2011

2009

2010

2017

2009

Current release

0.9.32, January 2024

3.2.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache version 2, commercial enterprise edition

commercial

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Erlang

C++

Java

Server operating systems

Linux
Unix
Windows

Linux
OS X

Appliance or cloud-service

Linux

Data scheme

schema-free

yes

schema-free

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

restricted

yes

SQL

Support of SQL

yes

SQL-like query language (GSQL)

APIs and other access methods

HTTP API
Native Erlang Interface

JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

TinkerPop 3

Supported programming languages

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

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

Groovy
Java

Server-side scripts

Stored procedures

Erlang

SQLScript, R

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

yes

none

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

none

Foreign keys

Referential integrity

links between data sets can be stored

yes

Relationships in graphs

yes

Relationships in graphs

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

optional

In-memory capabilities

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

yes

User concepts

Access control

yes, using Riak Security

yes

Role-based access control

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.