DBMS > Riak KV vs. Sequoiadb vs. Snowflake vs. SQream DB

System Properties Comparison Riak KV vs. Sequoiadb vs. Snowflake vs. SQream DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed, fault tolerant key-value store

NewSQL database with distributed OLTP and SQL

Cloud-based data warehousing service for structured and semi-structured data

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Key-value store

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

Document store
Relational DBMS

Relational DBMS

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

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

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

www.sequoiadb.com

www.snowflake.com

sqream.com

Technical documentation

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

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

docs.snowflake.net/manuals/index.html

docs.sqream.com

Developer

OpenSource, formerly Basho Technologies

Sequoiadb Ltd.

Snowflake Computing Inc.

SQream Technologies

Initial release

2009

2013

2014

2017

Current release

3.2.0, December 2022

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

Apache version 2, commercial enterprise edition

Open Source

Server: AGPL; Client: Apache V2

commercial

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

C++, CUDA, Haskell, Java, Scala

Server operating systems

Linux
OS X

Linux

hosted

Linux

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

yes

yes, ANSI Standard SQL Types

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

restricted

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

HTTP API
Native Erlang Interface

proprietary protocol using JSON

CLI Client
JDBC
ODBC

.Net
JDBC
ODBC

Supported programming languages

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

JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Erlang

JavaScript

user defined functions

user defined functions in Python

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Sharding

yes

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

yes

Transaction concepts

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

Document is locked during a transaction

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.

User concepts

Access control

yes, using Riak Security

simple password-based access control

Users with fine-grained authorization concept, user roles and pluggable authentication

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.