DBMS > Apache Doris vs. Atos Standard Common Repository vs. BigchainDB vs. Riak KV vs. Snowflake

System Properties Comparison Apache Doris vs. Atos Standard Common Repository vs. BigchainDB vs. Riak KV vs. Snowflake

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

An MPP-based analytics DBMS embracing the MySQL protocol

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

Distributed, fault tolerant key-value store

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

Primary database model

Relational DBMS

Document store
Key-value store

Document store

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.57
Rank	#244	Overall
	#113	Relational DBMS

Score	0.79
Rank	#212	Overall
	#36	Document stores

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

doris.apache.org
github.com/apache/doris

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.bigchaindb.com

www.snowflake.com

Technical documentation

github.com/apache/doris/wiki

bigchaindb.readthedocs.io/en/latest

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

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation, originally contributed from Baidu

Atos Convergence Creators

OpenSource, formerly Basho Technologies

Snowflake Computing Inc.

Initial release

2017

2016

2009

2014

Current release

1.2.2, February 2023

1703

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

AGPL v3

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

Java

Python

Erlang

Server operating systems

Linux

Linux
OS X

hosted

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

yes

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

Typing

predefined data types such as float or date

yes

optional

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

yes

APIs and other access methods

JDBC
MySQL client

LDAP

CLI Client
RESTful HTTP API

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Supported programming languages

Java

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
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

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

Sharding

cell division

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

fine grained access rights according to SQL-standard

LDAP bind authentication

yes

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.