DBMS > Graph Engine vs. Riak TS vs. RocksDB vs. TempoIQ vs. TerminusDB

System Properties Comparison Graph Engine vs. Riak TS vs. RocksDB vs. TempoIQ vs. TerminusDB

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Graph DBMS
Key-value store

Secondary database models

Document store
RDF store

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

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

www.graphengine.io

rocksdb.org

tempoiq.com (offline)

terminusdb.com

Technical documentation

www.graphengine.io/docs/manual

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

github.com/facebook/rocksdb/wiki

terminusdb.github.io/terminusdb/#

Developer

Microsoft

Open Source, formerly Basho Technologies

Facebook, Inc.

TempoIQ

DataChemist Ltd.

Initial release

2010

2015

2013

2012

2018

Current release

3.0.0, September 2022

9.2.1, May 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

BSD

commercial

Open Source

GPL V3

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

.NET and C

Erlang

C++

Prolog, Rust

Server operating systems

.NET

Linux
OS X

Linux

Data scheme

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

restricted

SQL

Support of SQL

yes, limited

SQL-like query language (WOQL)

APIs and other access methods

RESTful HTTP API

HTTP API
Native Erlang Interface

C++ API
Java API

HTTP API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C#
C++
F#
Visual Basic

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++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript

Node.js
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

yes

Erlang

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Realtime Alerts

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

horizontal partitioning

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

in-memory journaling

In-memory capabilities

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

yes

User concepts

Access control

simple authentication-based access control

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.