DBMS > Amazon Redshift vs. Kinetica vs. OpenTSDB vs. Snowflake vs. TerminusDB

System Properties Comparison Amazon Redshift vs. Kinetica vs. OpenTSDB vs. Snowflake vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Fully vectorized database across both GPUs and CPUs

Scalable Time Series DBMS based on HBase

Cloud-based data warehousing service for structured and semi-structured data

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

Primary database model

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
RDF store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

docs.kinetica.com

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

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

Developer

Amazon (based on PostgreSQL)

Kinetica

currently maintained by Yahoo and other contributors

Snowflake Computing Inc.

DataChemist Ltd.

Initial release

2012

2011

2014

2018

Current release

7.1, August 2021

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

LGPL

commercial

Open Source

GPL V3

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

C, C++

Java

Prolog, Rust

Server operating systems

hosted

Linux

Linux
Windows

hosted

Linux

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

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

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

HTTP API
Telnet API

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC

C++
Java
JavaScript (Node.js)
Python

Erlang
Go
Java
Python
R
Ruby

JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on HBase

yes

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

selectable replication factor

based on HBase

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

based on HBase

Immediate Consistency

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

in-memory journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

GPU vRAM or System RAM

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

Users with fine-grained authorization concept, user roles and pluggable authentication

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.