DBMS > Amazon Redshift vs. Graph Engine vs. Newts vs. SiteWhere vs. TimesTen

System Properties Comparison Amazon Redshift vs. Graph Engine vs. Newts vs. SiteWhere vs. TimesTen

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

Time Series DBMS based on Cassandra

M2M integration platform for persisting/querying time series data

In-Memory RDBMS compatible to Oracle

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Time Series DBMS

Relational 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	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

aws.amazon.com/redshift

www.graphengine.io

opennms.github.io/newts

github.com/sitewhere/sitewhere

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

docs.aws.amazon.com/redshift

www.graphengine.io/docs/manual

github.com/OpenNMS/newts/wiki

sitewhere1.sitewhere.io/index.html

docs.oracle.com/database/timesten-18.1

Developer

Amazon (based on PostgreSQL)

Microsoft

OpenNMS Group

SiteWhere

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2012

2010

2014

2010

1998

Current release

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache 2.0

Open Source

Common Public Attribution License Version 1.0

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

.NET and C

Java

Server operating systems

hosted

.NET

Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

schema-free

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

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

HTTP REST
Java API

HTTP REST

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
F#
Visual Basic

Java

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

user defined functions

in Python

yes

PL/SQL

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

based on Cassandra

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

selectable replication factor

based on HBase

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

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

by means of logfiles and checkpoints

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

fine grained access rights according to SQL-standard

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.