DBMS > JanusGraph vs. Riak TS vs. TempoIQ vs. Tkrzw

System Properties Comparison JanusGraph vs. Riak TS vs. TempoIQ vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Graph DBMS

Time Series DBMS

Key-value store

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

Score	1.85
Rank	#134	Overall
	#12	Graph DBMS

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

janusgraph.org

tempoiq.com (offline)

dbmx.net/tkrzw

Technical documentation

docs.janusgraph.org

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

Developer

Linux Foundation; originally developed as Titan by Aurelius

Open Source, formerly Basho Technologies

TempoIQ

Mikio Hirabayashi

Initial release

2017

2015

2012

2020

Current release

1.0.0, October 2023

3.0.0, September 2022

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

commercial

Open Source

Apache Version 2.0

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

Java

Erlang

C++

Server operating systems

Linux
OS X
Unix
Windows

Linux
OS X

Linux
macOS

Data scheme

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

yes

restricted

SQL

Support of SQL

yes, limited

APIs and other access methods

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

Clojure
Java
Python

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
JavaScript

Node.js
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

links between datasets 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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

In-memory capabilities

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

yes

using specific database classes

User concepts

Access control

User authentification and security via Rexster Graph Server

simple authentication-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.

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

Simple Deployment of a Graph Database: JanusGraph
12 October 2020, Towards Data Science

Database Deep Dives: JanusGraph
8 August 2019, IBM

JanusGraph Picks Up Where TitanDB Left Off
13 January 2017, Datanami

Nordstrom Builds Flexible Backend Ops with Kubernetes, Spark and JanusGraph
3 October 2019, The New Stack

From graph db to graph embedding. In 7 simple steps. | by Andy Greatorex
30 July 2020, Towards Data Science

provided by Google News

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page