DBMS > Atos Standard Common Repository vs. BigchainDB vs. Geode vs. Snowflake vs. Valentina Server

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. Geode vs. Snowflake vs. Valentina Server

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Object-relational database and reports server

Primary database model

Document store
Key-value store

Document store

Key-value store

Relational DBMS

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

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	0.18
Rank	#329	Overall
	#144	Relational DBMS

Website

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

Technical documentation

bigchaindb.readthedocs.io/en/latest

geode.apache.org/docs

docs.snowflake.net/manuals/index.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Atos Convergence Creators

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Snowflake Computing Inc.

Paradigma Software

Initial release

2016

2002

2014

1999

Current release

1703

1.1, February 2017

5.7.5

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Java

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Linux
OS X
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

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

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

SQL-like query language (OQL)

yes

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

CLI Client
JDBC
ODBC

ODBC

Supported programming languages

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
All JVM based languages
C++
Groovy
Java
Scala

JavaScript (Node.js)
Python

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Cache Event Listeners

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication

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

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

yes, on a single node

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

User concepts

Access control

LDAP bind authentication

yes

Access rights per client and object definable

Users with fine-grained authorization concept, user roles and pluggable 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.