DBMS > Atos Standard Common Repository vs. Blueflood vs. Faircom DB vs. RocksDB

System Properties Comparison Atos Standard Common Repository vs. Blueflood vs. Faircom DB vs. RocksDB

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.

Description

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

Scalable TimeSeries DBMS based on Cassandra

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store
Key-value store

Time Series DBMS

Key-value store
Relational DBMS

Key-value store

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

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

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

blueflood.io

www.faircom.com/products/faircom-db

rocksdb.org

Technical documentation

github.com/rax-maas/blueflood/wiki

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

github.com/facebook/rocksdb/wiki

Developer

Atos Convergence Creators

Rackspace

FairCom Corporation

Facebook, Inc.

Initial release

2016

2013

1979

2013

Current release

1703

V12, November 2020

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Restricted, free version available

Open Source

BSD

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

ANSI C, C++

C++

Server operating systems

Linux

Linux
OS X

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

Linux

Data scheme

Schema and schema-less with LDAP views

predefined scheme

schema free, schema optional, schema required, partial schema,

schema-free

Typing

predefined data types such as float or date

optional

yes

yes, ANSI SQL Types, JSON, typed binary structures

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, ANSI SQL with proprietary extensions

APIs and other access methods

LDAP

HTTP REST

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

C++ API
Java API

Supported programming languages

All languages with LDAP bindings

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

based on Cassandra

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes

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
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

tunable from ACID to Eventually Consistent

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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 with additional protections for files

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.