DBMS > Amazon Aurora vs. Riak TS vs. Sequoiadb vs. Spark SQL

System Properties Comparison Amazon Aurora vs. Riak TS vs. Sequoiadb vs. Spark SQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

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

NewSQL database with distributed OLTP and SQL

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

Primary database model

Relational DBMS

Time Series DBMS

Document store
Relational DBMS

Relational DBMS

Secondary database models

Document store

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

Score	12.46
Rank	#45	Overall
	#29	Relational DBMS

Score	0.25
Rank	#281	Overall
	#24	Time Series DBMS

Score	0.42
Rank	#256	Overall
	#39	Document stores
	#120	Relational DBMS

Score	22.86
Rank	#35	Overall
	#21	Relational DBMS

Website

aws.amazon.com/rds/aurora

riak.com/products/riak-ts

www.sequoiadb.com

spark.apache.org/sql

Technical documentation

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

www.sequoiadb.com/en/index.php?m=Files&a=index

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

Developer

Amazon

Basho Technologies

Sequoiadb Ltd.

Apache Software Foundation

Initial release

2015

2013

2014

Current release

3.2.0, October 2021

License

Commercial or Open Source

commercial

Open Source

Server: AGPL; Client: Apache V2

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

C++

Scala

Server operating systems

hosted

Linux
OS X

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

SQL

Support of SQL

yes

SQL-like query language

SQL-like DML and DDL statements

APIs and other access methods

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

proprietary protocol using JSON

JDBC
ODBC

Supported programming languages

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

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

.Net
C++
Java
PHP
Python

Java
Python
R
Scala

Server-side scripts

Stored procedures

yes

JavaScript and Erlang

JavaScript

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

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

ACID

Document is locked during a transaction

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

simple password-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.