DBMS > Axibase vs. Riak TS vs. Snowflake vs. Spark SQL vs. Transbase

System Properties Comparison Axibase vs. Riak TS vs. Snowflake vs. Spark SQL vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

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

Primary database model

Time Series DBMS

Relational DBMS

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

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

axibase.com/docs/atsd/finance

www.snowflake.com

spark.apache.org/sql

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

Technical documentation

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

docs.snowflake.net/manuals/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

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

Developer

Axibase Corporation

Open Source, formerly Basho Technologies

Snowflake Computing Inc.

Apache Software Foundation

Transaction Software GmbH

Initial release

2013

2015

2014

1987

Current release

15585

3.0.0, September 2022

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

commercial

Open Source

Apache 2.0

commercial

free development license

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

Scala

C and C++

Server operating systems

Linux

Linux
OS X

hosted

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

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

SQL-like query language

yes, limited

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Go
Java
PHP
Python
R
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

Java
Python
R
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

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

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes

none

Source-replica replication

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

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.

User concepts

Access control

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

fine grained access rights according to SQL-standard

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.