DBMS > Amazon Redshift vs. Graph Engine vs. OpenTSDB vs. SiteWhere

System Properties Comparison Amazon Redshift vs. Graph Engine vs. OpenTSDB 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 distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Scalable Time Series DBMS based on HBase

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Graph DBMS
Key-value store

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	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

aws.amazon.com/redshift

www.graphengine.io

opentsdb.net

github.com/sitewhere/sitewhere

Technical documentation

docs.aws.amazon.com/redshift

www.graphengine.io/docs/manual

opentsdb.net/docs/build/html/index.html

sitewhere1.sitewhere.io/index.html

Developer

Amazon (based on PostgreSQL)

Microsoft

currently maintained by Yahoo and other contributors

SiteWhere

Initial release

2012

2010

2011

2010

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

LGPL

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

.NET and C

Java

Server operating systems

hosted

.NET

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

predefined scheme

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

HTTP API
Telnet API

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
F#
Visual Basic

Erlang
Go
Java
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

based on HBase

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on HBase

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

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 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

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.