DBMS > AgensGraph vs. Amazon Aurora vs. Amazon Redshift vs. Apache Impala vs. Riak TS

System Properties Comparison AgensGraph vs. Amazon Aurora vs. Amazon Redshift vs. Apache Impala vs. Riak TS

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

MySQL and PostgreSQL compatible cloud service by Amazon

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for Hadoop

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Document store

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

bitnine.net/agensgraph

aws.amazon.com/rds/aurora

aws.amazon.com/redshift

impala.apache.org

Technical documentation

bitnine.net/documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

docs.aws.amazon.com/redshift

impala.apache.org/impala-docs.html

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

Developer

Bitnine Global Inc.

Amazon

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Open Source, formerly Basho Technologies

Initial release

2016

2015

2012

2013

2015

Current release

2.1, December 2018

4.1.0, June 2022

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2

Open Source

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++

Erlang

Server operating systems

Linux
OS X
Windows

hosted

Linux

Linux
OS X

Data scheme

depending on used data model

yes

schema-free

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.

yes

Secondary indexes

yes

restricted

yes

restricted

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes, limited

APIs and other access methods

Cypher Query Language
JDBC

ADO.NET
JDBC
ODBC

JDBC
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

C
Java
JavaScript
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

yes

user defined functions

in Python

yes

user defined functions and integration of map-reduce

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

links between datasets can be stored

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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.