DBMS > Atos Standard Common Repository vs. BigchainDB vs. Riak KV vs. SWC-DB

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. Riak KV vs. SWC-DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

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

A high performance, scalable Wide Column DBMS

Primary database model

Document store
Key-value store

Document store

Key-value store

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

Wide column store

Secondary database models

Time Series DBMS

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

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Score	0.01
Rank	#387	Overall
	#13	Wide column stores

Website

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

www.bigchaindb.com

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

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

Developer

Atos Convergence Creators

OpenSource, formerly Basho Technologies

Alex Kashirin

Initial release

2016

2009

2020

Current release

1703

3.2.0, December 2022

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPL V3

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Python

Erlang

C++

Server operating systems

Linux

Linux
OS X

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

optional

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

SQL-like query language

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

HTTP API
Native Erlang Interface

Proprietary protocol
Thrift

Supported programming languages

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

C++

Server-side scripts

Stored procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

Atomic execution of specific operations

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

LDAP bind authentication

yes

yes, using Riak Security

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Exploring the 10 BEST Python Libraries for Blockchain Applications
9 September 2023, DataDrivenInvestor

An Introduction to BigchainDB, a Popular Blockchain Database
17 September 2020, Open Source For You

Blockchain Database Startup BigchainDB Raises €3 Million
27 September 2016, CoinDesk

What is BigchainDB Technology & How it works and the Characteristics?
26 August 2017, Blockchain Council

Using BigchainDB: A Database with Blockchain Characteristics
20 January 2022, Open Source For You

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Photos: Woodstock music graduate Alex Riak returns to work with students
11 December 2023, Shaw Local News Network

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

provided by Google News

2022 All O-Zone Football Team
17 December 2022, Ozarks Sports Zone

provided by Google News

Share this page