DBMS > Hazelcast vs. Riak TS vs. Snowflake vs. SWC-DB

System Properties Comparison Hazelcast vs. Riak TS vs. Snowflake vs. SWC-DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

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

A high performance, scalable Wide Column DBMS

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Time Series DBMS

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

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

hazelcast.com

www.snowflake.com

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

hazelcast.org/imdg/docs

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

docs.snowflake.net/manuals/index.html

Developer

Hazelcast

Open Source, formerly Basho Technologies

Snowflake Computing Inc.

Alex Kashirin

Initial release

2008

2015

2014

2020

Current release

5.3.6, November 2023

3.0.0, September 2022

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

commercial

Open Source

GPL 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

Java

Erlang

C++

Server operating systems

All OS with a Java VM

Linux
OS X

hosted

Linux

Data scheme

schema-free

yes

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

schema-free

Typing

predefined data types such as float or date

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

restricted

SQL

Support of SQL

SQL-like query language

yes, limited

yes

SQL-like query language

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Proprietary protocol
Thrift

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

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

C++

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

Erlang

user defined functions

Triggers

yes

Events

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

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

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 or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between datasets can be stored

yes

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

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.

yes

User concepts

Access control

Role-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.