DBMS > Atos Standard Common Repository vs. Blueflood vs. Transwarp ArgoDB vs. Vitess vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. Blueflood vs. Transwarp ArgoDB vs. Vitess vs. Yaacomo

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

Scalable TimeSeries DBMS based on Cassandra

Distributed Analytical Database to replace Hadoop+MPP hybrid architecture

Scalable, distributed, cloud-native DBMS, extending MySQL

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

Primary database model

Document store
Key-value store

Time Series DBMS

Relational DBMS

Secondary database models

Search engine

Document store
Spatial DBMS

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

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	0.12
Rank	#348	Overall
	#151	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

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

blueflood.io

www.transwarp.cn/en/product/argodb

vitess.io

yaacomo.com

Technical documentation

github.com/rax-maas/blueflood/wiki

docs.transwarp.cn/#/documents-support/docs?category=ARGODB

vitess.io/docs

Developer

Atos Convergence Creators

Rackspace

Transwarp

The Linux Foundation, PlanetScale

Q2WEB GmbH

Initial release

2016

2013

2009

Current release

1703

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2.0, commercial licenses available

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

Server operating systems

Linux

Linux
OS X

Docker
Linux
macOS

Android
Linux
Windows

Data scheme

Schema and schema-less with LDAP views

predefined scheme

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

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

LDAP

HTTP REST

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

based on Cassandra

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

Atomic execution of specific operations

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

no user groups or roles

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

Real-Time Performance and Health Monitoring Using Netdata
2 September 2019, CNX Software

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page