DBMS > Amazon Redshift vs. JanusGraph vs. MarkLogic vs. SiteWhere

System Properties Comparison Amazon Redshift vs. JanusGraph vs. MarkLogic vs. SiteWhere

Please select another system to include it in the comparison.

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

Operational and transactional Enterprise NoSQL database

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Graph DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

aws.amazon.com/redshift

janusgraph.org

www.marklogic.com

github.com/sitewhere/sitewhere

Technical documentation

docs.aws.amazon.com/redshift

docs.janusgraph.org

docs.marklogic.com

sitewhere1.sitewhere.io/index.html

Developer

Amazon (based on PostgreSQL)

Linux Foundation; originally developed as Titan by Aurelius

MarkLogic Corp.

SiteWhere

Initial release

2012

2017

2001

2010

Current release

0.6.3, February 2023

11.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

Common Public Attribution License Version 1.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

C++

Java

Server operating systems

hosted

Linux
OS X
Unix
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

Schema can be enforced

predefined scheme

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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL92

APIs and other access methods

JDBC
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java
Python

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via XQuery or JavaScript

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

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

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

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

yes, with Range Indexes

User concepts

Access control

fine grained access rights according to SQL-standard

User authentification and security via Rexster Graph Server

Role-based access control at the document and subdocument levels

Users with fine-grained authorization concept

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.