DBMS > Atos Standard Common Repository vs. BigchainDB vs. Hazelcast vs. Ignite vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. Hazelcast vs. Ignite 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

A widely adopted in-memory data grid

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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

Primary database model

Document store
Key-value store

Document store

Key-value store

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

Technical documentation

bigchaindb.readthedocs.io/en/latest

hazelcast.org/imdg/docs

apacheignite.readme.io/docs

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Hazelcast

Apache Software Foundation

Snowflake Computing Inc.

Initial release

2016

2008

2015

2014

Current release

1703

5.3.6, November 2023

Apache Ignite 2.6

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

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

C++, Java, .Net

Server operating systems

Linux

All OS with a Java VM

Linux
OS X
Solaris
Windows

hosted

Data scheme

Schema and schema-less with LDAP views

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

yes

Events

yes (cache interceptors and events)

similar concept for controling cloud resources

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

yes

Replicated Map

yes (replicated cache)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

one or two-phase-commit; repeatable reads; read commited

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

Role-based access control

Security Hooks for custom implementations

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.