DBMS > JanusGraph vs. Microsoft Azure Table Storage vs. OpenMLDB vs. SAP HANA vs. TigerGraph

System Properties Comparison JanusGraph vs. Microsoft Azure Table Storage vs. OpenMLDB vs. SAP HANA vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

A Graph DBMS optimized for distributed clusters

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

A Wide Column Store for rapid development using massive semi-structured datasets

An open-source machine learning database that provides a feature platform for training and inference

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

Primary database model

Secondary database models

Relational DBMS

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.94
Rank	#129	Overall
	#12	Graph DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.02
Rank	#367	Overall
	#37	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

janusgraph.org

azure.microsoft.com/en-us/services/storage/tables

openmldb.ai

www.sap.com/products/hana.html

www.tigergraph.com

Technical documentation

docs.janusgraph.org

openmldb.ai/docs/zh/main

help.sap.com/hana

docs.tigergraph.com

Developer

Linux Foundation; originally developed as Titan by Aurelius

Microsoft

4 Paradigm Inc.

SAP

Initial release

2017

2012

2020

2010

2017

Current release

0.6.3, February 2023

2024-2 February 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

commercial

Cloud-based only

Only available as a cloud service

yes

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

Java

C++, Java, Scala

C++

Server operating systems

Linux
OS X
Unix
Windows

hosted

Linux

Appliance or cloud-service

Linux

Data scheme

yes

schema-free

Fixed schema

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

SQL

Support of SQL

yes

SQL-like query language (GSQL)

APIs and other access methods

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

RESTful HTTP API

JDBC
SQLAlchemy

JDBC
ODBC

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

Supported programming languages

Clojure
Java
Python

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

C++
Go
Java
Python
Scala

C++
Java

Server-side scripts

Stored procedures

yes

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

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

Sharding

Implicit feature of the cloud service

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Source-replica replication

yes

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Relationships in graphs

Transaction concepts

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

ACID

optimistic locking

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

User concepts

Access control

User authentification and security via Rexster Graph Server

Access rights based on private key authentication or shared access signatures

fine grained access rights according to SQL-standard

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.