DBMS > Atos Standard Common Repository vs. BigchainDB vs. Machbase Neo vs. searchxml vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. Machbase Neo vs. searchxml vs. Snowflake

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

TimeSeries DBMS for AIoT and BigData

DBMS for structured and unstructured content wrapped with an application server

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

Primary database model

Document store
Key-value store

Document store

Time Series DBMS

Native XML DBMS
Search engine

Relational DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.bigchaindb.com

machbase.com

www.searchxml.net/category/products

www.snowflake.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

machbase.com/dbms

www.searchxml.net/support/handouts

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Machbase

informationpartners gmbh

Snowflake Computing Inc.

Initial release

2016

2013

2015

2014

Current release

1703

V8.0, August 2023

1.0

License

Commercial or Open Source

commercial

Open Source

AGPL v3

commercial

free test version available

commercial

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++

Server operating systems

Linux

Linux
macOS
Windows

Windows

hosted

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

schema-free

yes

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

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

SQL-like query language

yes

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

RESTful HTTP API
WebDAV
XQuery
XSLT

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C++

most other programming languages supported via APIs

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

on the application server

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

yes

sychronisation to multiple collections

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

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

multiple readers, single writer

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

volatile and lookup table

User concepts

Access control

LDAP bind authentication

yes

simple password-based access control

Domain, group and role-based access control at the document level and for application services

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

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.