DBMS > GBase vs. Riak TS vs. Rockset vs. Snowflake

System Properties Comparison GBase vs. Riak TS vs. Rockset vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

Primary database model

Secondary database models

Relational DBMS
Search engine

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

Score	1.05
Rank	#186	Overall
	#86	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.gbase.cn

rockset.com

www.snowflake.com

Technical documentation

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

docs.rockset.com

docs.snowflake.net/manuals/index.html

Developer

General Data Technology Co., Ltd.

Open Source, formerly Basho Technologies

Rockset

Snowflake Computing Inc.

Initial release

2004

2015

2019

2014

Current release

GBase 8a, GBase 8s, GBase 8c

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

commercial

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

C, Java, Python

Erlang

C++

Server operating systems

Linux

Linux
OS X

hosted

Data scheme

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

dynamic typing

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

ingestion from XML files supported

yes

Secondary indexes

yes

restricted

all fields are automatically indexed

SQL

Support of SQL

Standard with numerous extensions

yes, limited

Read-only SQL queries, including JOINs

yes

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

HTTP API
Native Erlang Interface

HTTP REST

CLI Client
JDBC
ODBC

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

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

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

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

Automatic sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

In-memory capabilities

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

User concepts

Access control

yes

Access rights for users and organizations can be defined via Rockset console

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.