DBMS > Atos Standard Common Repository vs. BigchainDB vs. Snowflake vs. Tibero vs. Tkrzw

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. Snowflake vs. Tibero vs. Tkrzw

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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Cloud-based data warehousing service for structured and semi-structured data

A secure RDBMS, designed for easy portability from Oracle

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Key-value store

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

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

www.bigchaindb.com

www.snowflake.com

us.tmaxsoft.com/products/tibero

dbmx.net/tkrzw

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.snowflake.net/manuals/index.html

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Atos Convergence Creators

Snowflake Computing Inc.

TmaxSoft

Mikio Hirabayashi

Initial release

2016

2014

2003

2020

Current release

1703

6, April 2015

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

AGPL v3

commercial

Open Source

Apache Version 2.0

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

Python

C and Assembler

C++

Server operating systems

Linux

hosted

AIX
HP-UX
Linux
Solaris
Windows

Linux
macOS

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

SQL

Support of SQL

yes

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

CLI Client
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

JavaScript (Node.js)
Python

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Persistent Stored Procedure (PSM)

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

yes

horizontal partitioning

by range, hash, list or composite

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

yes

Multi-source replication
Source-replica replication

none

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

Immediate Consistency

Foreign keys

Referential integrity

yes

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

yes,with MongoDB ord RethinkDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

planned for next version

yes

using specific database classes

User concepts

Access control

LDAP bind authentication

yes

Users with fine-grained authorization concept, user roles and pluggable authentication

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.