DBMS > Atos Standard Common Repository vs. LevelDB vs. Riak TS vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. LevelDB vs. Riak TS 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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

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

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

Time Series DBMS

Relational DBMS

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

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

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

github.com/google/leveldb

yaacomo.com

Technical documentation

github.com/google/leveldb/blob/main/doc/index.md

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

Developer

Atos Convergence Creators

Google

Open Source, formerly Basho Technologies

Q2WEB GmbH

Initial release

2016

2011

2015

2009

Current release

1703

1.23, February 2021

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

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

C++

Erlang

Server operating systems

Linux

Illumos
Linux
OS X
Windows

Linux
OS X

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

yes, limited

yes

APIs and other access methods

LDAP

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

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

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

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

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between datasets 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

with automatic compression on writes

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

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

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

LevelDB in Ruby — SitePoint
22 October 2014, SitePoint

Microsoft Teams stores auth tokens as cleartext in Windows, Linux, Macs
14 September 2022, BleepingComputer

Pliops unveils XDP-Rocks for RocksDB – Blocks and Files
19 October 2022, Blocks and Files

XanMod, Liquorix Kernels Offer Some Advantages On AMD Ryzen 5 Notebook
26 July 2021, Phoronix

Rust-Based Info Stealers Abuse GitHub Codespaces
19 May 2023, Trend Micro

provided by Google News

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

Enterprise NoSQL Database for the IoT Becomes Open Source
11 May 2016, ENGINEERING.com

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page