DBMS > AlaSQL vs. BigchainDB vs. Cubrid vs. Riak KV vs. Snowflake

System Properties Comparison AlaSQL vs. BigchainDB vs. Cubrid vs. Riak KV vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

Distributed, fault tolerant key-value store

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

Primary database model

Document store
Relational DBMS

Document store

Relational DBMS

Key-value store

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

Relational DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

alasql.org

www.bigchaindb.com

cubrid.com (korean)
cubrid.org (english)

www.snowflake.com

Technical documentation

github.com/AlaSQL/alasql

bigchaindb.readthedocs.io/en/latest

cubrid.org/manuals

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

docs.snowflake.net/manuals/index.html

Developer

Andrey Gershun & Mathias R. Wulff

CUBRID Corporation, CUBRID Foundation

OpenSource, formerly Basho Technologies

Snowflake Computing Inc.

Initial release

2014

2016

2008

2009

2014

Current release

11.0, January 2021

3.2.0, December 2022

License

Commercial or Open Source

Open Source

MIT-License

Open Source

AGPL v3

Open Source

Apache Version 2.0

Open Source

Apache version 2, commercial enterprise edition

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

JavaScript

Python

C, C++, Java

Erlang

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Linux
Windows

Linux
OS X

hosted

Data scheme

schema-free

yes

schema-free

yes

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

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

Close to SQL99, but no user access control, stored procedures and host language bindings.

yes

APIs and other access methods

JavaScript API

CLI Client
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Supported programming languages

JavaScript

Go
Haskell
Java
JavaScript
Python
Ruby

C
C#
C++
Go
Java
JavaScript (Node.js)
Perl
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

Server-side scripts

Stored procedures

Java Stored Procedures

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

none

Sharding

none

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Source-replica 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

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes,with MongoDB ord RethinkDB

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

yes

fine grained access rights according to SQL-standard

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.