DBMS > Riak TS vs. Snowflake vs. Sphinx vs. WakandaDB

System Properties Comparison Riak TS vs. Snowflake vs. Sphinx vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Open source search engine for searching in data from different sources, e.g. relational databases

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

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

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

www.snowflake.com

sphinxsearch.com

wakanda.github.io

Technical documentation

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

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

wakanda.github.io/doc

Developer

Open Source, formerly Basho Technologies

Snowflake Computing Inc.

Sphinx Technologies Inc.

Wakanda SAS

Initial release

2015

2014

2001

2012

Current release

3.0.0, September 2022

3.5.1, February 2023

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

commercial

Open Source

GPL version 2, commercial licence available

Open Source

AGPLv3, extended commercial license available

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

Server operating systems

Linux
OS X

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Windows

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

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

full-text index on all search fields

SQL

Support of SQL

yes, limited

yes

SQL-like query language (SphinxQL)

APIs and other access methods

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Proprietary protocol

RESTful HTTP API

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

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

JavaScript

Server-side scripts

Stored procedures

Erlang

user defined functions

yes

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

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 datasets can be stored

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

yes

In-memory capabilities

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

User concepts

Access control

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

yes

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.