DBMS > Amazon Redshift vs. OpenTSDB vs. Teradata Aster vs. TigerGraph vs. Warp 10

System Properties Comparison Amazon Redshift vs. OpenTSDB vs. Teradata Aster vs. TigerGraph vs. Warp 10

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Scalable Time Series DBMS based on HBase

Platform for big data analytics on multistructured data sources and types

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

aws.amazon.com/redshift

opentsdb.net

www.tigergraph.com

www.warp10.io

Technical documentation

docs.aws.amazon.com/redshift

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

docs.tigergraph.com

www.warp10.io/content/02_Getting_started

Developer

Amazon (based on PostgreSQL)

currently maintained by Yahoo and other contributors

Teradata

SenX

Initial release

2012

2011

2005

2017

2015

License

Commercial or Open Source

commercial

Open Source

LGPL

commercial

Open Source

Apache License 2.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
Windows

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

yes

schema-free

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.

yes

in Aster File Store

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC

HTTP API
Telnet API

ADO.NET
JDBC
ODBC
OLE DB

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

HTTP API
Jupyter
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

Erlang
Go
Java
Python
R
Ruby

C
C#
C++
Java
Python
R

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

R packages

yes

WarpScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

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

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

based on HBase

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Role-based access control

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.