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

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

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.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

Distributed, fault tolerant key-value store

A high performance, scalable Wide Column DBMS

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Key-value store

Key-value store

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

Wide column store

Relational DBMS

Secondary database models

Time Series DBMS

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

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

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

yaacomo.com

Technical documentation

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

Developer

Atos Convergence Creators

OpenSource, formerly Basho Technologies

Alex Kashirin

Q2WEB GmbH

Initial release

2016

2009

2020

2009

Current release

1703

3.2.0, December 2022

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPL V3

commercial

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

Erlang

C++

Server operating systems

Linux

Linux
OS X

Linux

Android
Linux
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

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

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

LDAP

HTTP API
Native Erlang Interface

Proprietary protocol
Thrift

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

no "single point of failure"

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Source-replica replication

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

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

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, using Riak Security

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.

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

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

Basho Revamps Riak Open-Source Database
17 September 2014, InformationWeek

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

Riak Taps Mesos for 'Push Button' NoSQL Scalability
20 August 2015, Datanami

provided by Google News

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

provided by Google News

Share this page