DBMS > EXASOL vs. HarperDB vs. Riak KV vs. Snowflake

System Properties Comparison EXASOL vs. HarperDB vs. Riak KV vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Distributed, fault tolerant key-value store

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

Primary database model

Relational DBMS

Document store

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	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	0.60
Rank	#244	Overall
	#38	Document stores

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

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.exasol.com

www.harperdb.io

www.snowflake.com

Technical documentation

www.exasol.com/resources

docs.harperdb.io/docs

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

docs.snowflake.net/manuals/index.html

Developer

Exasol

HarperDB

OpenSource, formerly Basho Technologies

Snowflake Computing Inc.

Initial release

2000

2017

2009

2014

Current release

3.1, August 2021

3.2.0, December 2022

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache version 2, commercial enterprise edition

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

Node.js

Erlang

Server operating systems

Linux
OS X

hosted

Data scheme

yes

dynamic schema

schema-free

yes

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

Typing

predefined data types such as float or date

yes

JSON data types

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

SQL

Support of SQL

yes

SQL-like data manipulation statements

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Custom Functions

since release 3.1

Erlang

user defined functions

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

A table resides as a whole on one (or more) nodes in a cluster

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

the nodes on which a table resides can be defined

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

Access rights for users, groups and roles according to SQL-standard

Access rights for users and roles

yes, using Riak Security

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.