DBMS > Amazon Redshift vs. JanusGraph vs. SiteWhere vs. TerminusDB vs. TigerGraph

System Properties Comparison Amazon Redshift vs. JanusGraph vs. SiteWhere vs. TerminusDB vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A Graph DBMS optimized for distributed clusters

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

M2M integration platform for persisting/querying time series data

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

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

Primary database model

Secondary database models

Document store
RDF store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

aws.amazon.com/redshift

janusgraph.org

github.com/sitewhere/sitewhere

terminusdb.com

www.tigergraph.com

Technical documentation

docs.aws.amazon.com/redshift

docs.janusgraph.org

sitewhere1.sitewhere.io/index.html

terminusdb.github.io/terminusdb/#

docs.tigergraph.com

Developer

Amazon (based on PostgreSQL)

Linux Foundation; originally developed as Titan by Aurelius

SiteWhere

DataChemist Ltd.

Initial release

2012

2017

2010

2018

2017

Current release

0.6.3, February 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Common Public Attribution License Version 1.0

Open Source

GPL V3

commercial

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

Prolog, Rust

C++

Server operating systems

hosted

Linux
OS X
Unix
Windows

Linux
OS X
Windows

Linux

Data scheme

yes

predefined scheme

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

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (WOQL)

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

HTTP REST

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

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

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java
Python

JavaScript
Python

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

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

Sharding

based on HBase

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on HBase

Journaling Streams

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

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

yes

in-memory journaling

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

fine grained access rights according to SQL-standard

User authentification and security via Rexster Graph Server

Users with fine-grained authorization concept

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.