DBMS > RavenDB vs. Riak KV vs. Snowflake vs. SWC-DB

System Properties Comparison RavenDB vs. Riak KV vs. Snowflake vs. SWC-DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open Source Operational and Transactional Enterprise NoSQL Document Database

Distributed, fault tolerant key-value store

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

A high performance, scalable Wide Column DBMS

Primary database model

Document store

Key-value store

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

Relational DBMS

Wide column store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Time Series DBMS

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

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

ravendb.net

www.snowflake.com

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

Technical documentation

ravendb.net/docs

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

docs.snowflake.net/manuals/index.html

Developer

Hibernating Rhinos

OpenSource, formerly Basho Technologies

Snowflake Computing Inc.

Alex Kashirin

Initial release

2010

2009

2014

2020

Current release

5.4, July 2022

3.2.0, December 2022

0.5, April 2021

License

Commercial or Open Source

Open Source

AGPL version 3, commercial license available

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

C++

Server operating systems

Linux
macOS
Raspberry Pi
Windows

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

Secondary indexes

yes

restricted

SQL

Support of SQL

SQL-like query language (RQL)

yes

SQL-like query language

APIs and other access methods

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Proprietary protocol
Thrift

Supported programming languages

.Net
C#
F#
Go
Java
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

C++

Server-side scripts

Stored procedures

yes

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

no "single point of failure"

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

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

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

ACID, Cluster-wide transaction available

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

Authorization levels configured per client per database

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.