DBMS > Riak TS vs. Snowflake vs. Transbase vs. Warp 10

System Properties Comparison Riak TS vs. Snowflake vs. Transbase vs. Warp 10

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

A resource-optimized, high-performance, universally applicable RDBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Time Series DBMS

Relational DBMS

Time Series DBMS

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

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

www.snowflake.com

www.transaction.de/en/products/transbase.html

www.warp10.io

Technical documentation

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

docs.snowflake.net/manuals/index.html

www.transaction.de/en/products/transbase/features.html

www.warp10.io/content/02_Getting_started

Developer

Open Source, formerly Basho Technologies

Snowflake Computing Inc.

Transaction Software GmbH

SenX

Initial release

2015

2014

1987

2015

Current release

3.0.0, September 2022

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

commercial

free development license

Open Source

Apache License 2.0

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 and C++

Java

Server operating systems

Linux
OS X

hosted

FreeBSD
Linux
macOS
Solaris
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

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

yes

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

restricted

yes

SQL

Support of SQL

yes, limited

yes

APIs and other access methods

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Jupyter
WebSocket

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
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

Erlang

user defined functions

yes

WarpScript

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

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Source-replica replication

selectable replication factor

based on HBase

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

based on HBase

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

yes

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

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

fine grained access rights according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.