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

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

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

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.27
Rank	#292	Overall
	#132	Relational DBMS

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Website

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

brytlyt.io

yanza.com

Technical documentation

docs.brytlyt.io

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

Developer

Atos Convergence Creators

Brytlyt

Open Source, formerly Basho Technologies

Yanza

Initial release

2016

2015

Current release

1703

5.0, August 2023

3.0.0, September 2022

License

Commercial or Open Source

commercial

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

C, C++ and CUDA

Erlang

Server operating systems

Linux

Linux
OS X
Windows

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

yes, limited

APIs and other access methods

LDAP

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

All languages with LDAP bindings

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

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

user defined functions

in PL/pgSQL

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

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

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

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

Opensignal Announces Acquisition of Brytlyt GPU-based Data Analytics & Visualization Technology
5 June 2024, PR Web

Brytlyt releases version 5.0, introducing a more intuitive, intelligent and flexible analytics platform
1 August 2023, PR Newswire

Bringing GPUs To Bear On Bog Standard Relational Databases
26 February 2018, The Next Platform

London’s Brytlyt raises €4.4 million for its data analytics and visualisation technology
22 December 2021, EU-Startups

Brytlyt Unleashes Serverless GPU-Acceleration for Analytics
15 September 2021, PR Newswire

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