DBMS > Amazon Redshift vs. Ingres vs. Riak KV vs. Spark SQL vs. Trafodion

System Properties Comparison Amazon Redshift vs. Ingres vs. Riak KV vs. Spark SQL vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Well established RDBMS

Distributed, fault tolerant key-value store

Spark SQL is a component on top of 'Spark Core' for structured data processing

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Website

aws.amazon.com/redshift

www.actian.com/databases/ingres

spark.apache.org/sql

trafodion.apache.org

Technical documentation

docs.aws.amazon.com/redshift

docs.actian.com/ingres

www.tiot.jp/riak-docs/riak/kv/latest

spark.apache.org/docs/latest/sql-programming-guide.html

trafodion.apache.org/documentation.html

Developer

Amazon (based on PostgreSQL)

Actian Corporation

OpenSource, formerly Basho Technologies

Apache Software Foundation

Apache Software Foundation, originally developed by HP

Initial release

2012

1974

originally developed at University Berkely in early 1970s

2009

2014

Current release

11.2, May 2022

3.2.0, December 2022

3.5.0 ( 2.13), September 2023

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

Apache 2.0

Open Source

Apache 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

Erlang

Scala

C++, Java

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux
OS X

Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

restricted

yes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

HTTP API
Native Erlang Interface

JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Java
Python
R
Scala

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Erlang

Java Stored Procedures

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

no "single point of failure"

yes, utilizing Spark Core

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Ingres Replicator

selectable replication factor

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

links between data sets can be stored

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

yes, using Riak Security

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.