DBMS > Amazon Redshift vs. Riak TS vs. Sqrrl vs. ToroDB

System Properties Comparison Amazon Redshift vs. Riak TS vs. Sqrrl vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

ToroDB 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

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

Adaptable, secure NoSQL built on Apache Accumulo

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	0.25
Rank	#308	Overall
	#26	Time Series DBMS

Website

aws.amazon.com/redshift

sqrrl.com

github.com/torodb/server

Technical documentation

docs.aws.amazon.com/redshift

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

Developer

Amazon (based on PostgreSQL)

Open Source, formerly Basho Technologies

Amazon

originally Sqrrl Data, Inc.

8Kdata

Initial release

2012

2015

2012

2016

Current release

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

commercial

Open Source

AGPL-V3

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

Java

Server operating systems

hosted

Linux
OS X

Linux

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

yes, limited

APIs and other access methods

JDBC
ODBC

HTTP API
Native Erlang Interface

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

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

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

user defined functions

in Python

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

making use of Hadoop

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

making use of Hadoop

Source-replica replication

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

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Eventual Consistency
Immediate 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

Atomic updates per row, document, or graph entity

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

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

Access rights for users and roles

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.