DBMS > Amazon Redshift vs. Hive vs. IRONdb vs. Kinetica vs. RDF4J

System Properties Comparison Amazon Redshift vs. Hive vs. IRONdb vs. Kinetica vs. RDF4J

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

data warehouse software for querying and managing large distributed datasets, built on Hadoop

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Fully vectorized database across both GPUs and CPUs

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Secondary database models

Spatial DBMS
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	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Website

aws.amazon.com/redshift

hive.apache.org

www.circonus.com/solutions/time-series-database/

www.kinetica.com

rdf4j.org

Technical documentation

docs.aws.amazon.com/redshift

cwiki.apache.org/confluence/display/Hive/Home

docs.circonus.com/irondb/category/getting-started

docs.kinetica.com

rdf4j.org/documentation

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

initially developed by Facebook

Circonus LLC.

Kinetica

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2012

2017

2012

2004

Current release

3.1.3, April 2022

V0.10.20, January 2018

7.1, August 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

Open Source

Eclipse Distribution License (EDL), v1.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 and C++

C, C++

Java

Server operating systems

hosted

All OS with a Java VM

Linux

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

yes

RDF Schemas

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL-like DML and DDL statements

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Thrift

HTTP API

JDBC
ODBC
RESTful HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

All languages supporting JDBC/ODBC

C++
Java
PHP
Python

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C++
Java
JavaScript (Node.js)
Python

Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions and integration of map-reduce

yes, in Lua

user defined functions

yes

Triggers

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

configurable replication factor, datacenter aware

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate consistency per node, eventual consistency across nodes

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

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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, groups and roles

Access rights for users and roles on table level

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.