DBMS > Atos Standard Common Repository vs. Databend vs. Riak TS vs. Yanza

System Properties Comparison Atos Standard Common Repository vs. Databend vs. Riak TS vs. Yanza

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.

Yanza 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

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

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

Time Series DBMS for IoT Applications

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.28
Rank	#287	Overall
	#131	Relational DBMS

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Website

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

github.com/datafuselabs/databend
www.databend.com

yanza.com

Technical documentation

docs.databend.com

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

Developer

Atos Convergence Creators

Databend Labs

Open Source, formerly Basho Technologies

Yanza

Initial release

2016

2021

2015

Current release

1703

1.0.59, April 2023

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Rust

Erlang

Server operating systems

Linux

hosted
Linux
macOS

Linux
OS X

Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

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

SQL

Support of SQL

yes

yes, limited

APIs and other access methods

LDAP

CLI Client
JDBC
RESTful HTTP API

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

All languages with LDAP bindings

Go
Java
JavaScript (Node.js)
Python
Rust

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

selectable replication factor

none

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

Transaction concepts

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

Atomic execution of specific operations

yes

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

Users with fine-grained authorization concept, user roles

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

Apache Iceberg Rust Released
9 September 2024, iProgrammer

Â£1.1 Million in AddisonMckee Tube Bending Technologies Provides Dinex with Outstanding OEM Credentials
24 May 2007, Thomasnet

provided by Google News

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

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

provided by Google News

Share this page