DBMS > Atos Standard Common Repository vs. Drizzle vs. Hyprcubd vs. Riak TS

System Properties Comparison Atos Standard Common Repository vs. Drizzle vs. Hyprcubd vs. Riak TS

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.

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Serverless Time Series DBMS

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

Primary database model

Document store
Key-value store

Relational DBMS

Time Series DBMS

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

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

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

hyprcubd.com (offline)

Technical documentation

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

Developer

Atos Convergence Creators

Drizzle project, originally started by Brian Aker

Hyprcubd, Inc.

Open Source, formerly Basho Technologies

Initial release

2016

2008

2015

Current release

1703

7.2.4, September 2012

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

Open Source

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

C++

Erlang

Server operating systems

Linux

FreeBSD
Linux
OS X

hosted

Linux
OS X

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

optional

yes

time, int, uint, float, string

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

with proprietary extensions

SQL-like query language

yes, limited

APIs and other access methods

LDAP

JDBC

gRPC (https)

HTTP API
Native Erlang Interface

Supported programming languages

All languages with LDAP bindings

C
C++
Java
PHP

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

hooks for callbacks inside the server can be used.

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

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

Foreign keys

Referential integrity

yes

links between datasets can be stored

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

token access

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

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

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

provided by Google News

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

provided by Google News

Share this page