DBMS > Amazon Redshift vs. GridDB vs. Kinetica vs. SiteWhere

System Properties Comparison Amazon Redshift vs. GridDB vs. Kinetica 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

Scalable in-memory time series database optimized for IoT and Big Data

Fully vectorized database across both GPUs and CPUs

M2M integration platform for persisting/querying time series data

Primary database model

Secondary database models

Key-value store
Relational DBMS

Spatial DBMS
Time Series DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	0.42
Rank	#261	Overall
	#120	Relational DBMS

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Website

aws.amazon.com/redshift

griddb.net

www.kinetica.com

github.com/sitewhere/sitewhere

Technical documentation

docs.aws.amazon.com/redshift

docs.griddb.net

docs.kinetica.com

sitewhere1.sitewhere.io/index.html

Developer

Amazon (based on PostgreSQL)

Toshiba Corporation

Kinetica

SiteWhere

Initial release

2012

2013

2012

2010

Current release

5.1, August 2022

7.1, August 2021

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

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

C++

C, C++

Java

Server operating systems

hosted

Linux

Linux
OS X
Windows

Data scheme

yes

predefined scheme

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

JDBC
ODBC
RESTful HTTP API

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

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

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Triggers

yes

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Immediate Consistency or Eventual Consistency depending on configuration

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

ACID at container level

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

GPU vRAM or System RAM

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

Access rights for users and roles on table level

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.