DBMS > HarperDB vs. NuoDB vs. Riak TS vs. Snowflake

System Properties Comparison HarperDB vs. NuoDB vs. Riak TS vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

NuoDB is a webscale distributed database that supports SQL and ACID transactions

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

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

Primary database model

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

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	0.94
Rank	#197	Overall
	#92	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.harperdb.io

www.3ds.com/nuodb-distributed-sql-database

www.snowflake.com

Technical documentation

docs.harperdb.io/docs

doc.nuodb.com

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

docs.snowflake.net/manuals/index.html

Developer

HarperDB

Dassault Systèmes

originally NuoDB, Inc.

Open Source, formerly Basho Technologies

Snowflake Computing Inc.

Initial release

2017

2013

2015

2014

Current release

3.1, August 2021

3.0.0, September 2022

License

Commercial or Open Source

commercial

free community edition available

commercial

limited edition free

Open Source

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

C++

Erlang

Server operating systems

Linux
OS X

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

Linux
OS X

hosted

Data scheme

dynamic schema

yes

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

SQL-like data manipulation statements

yes

yes, limited

yes

APIs and other access methods

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Supported programming languages

.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

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

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

Custom Functions

since release 3.1

Java, SQL

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

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

data is dynamically stored/cached on the nodes where it is read/written

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

the nodes on which a table resides can be defined

yes

Managed transparently by NuoDB

selectable replication factor

yes

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

Foreign keys

Referential integrity

yes

links between datasets can be stored

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

tunable commit protocol

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

Durability

Support for making data persistent

yes, using LMDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Temporary table

User concepts

Access control

Access rights for users and roles

Standard SQL roles/ privileges, Administrative Users

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.