DBMS > Atos Standard Common Repository vs. Ehcache vs. OpenQM vs. Snowflake vs. SWC-DB

System Properties Comparison Atos Standard Common Repository vs. Ehcache vs. OpenQM vs. Snowflake vs. SWC-DB

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

A widely adopted Java cache with tiered storage options

QpenQM is a high-performance, self-tuning, multi-value DBMS

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

A high performance, scalable Wide Column DBMS

Primary database model

Document store
Key-value store

Secondary database models

Time Series DBMS

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

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

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

www.ehcache.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.snowflake.com

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

www.ehcache.org/documentation

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Terracotta Inc, owned by Software AG

Rocket Software, originally Martin Phillips

Snowflake Computing Inc.

Alex Kashirin

Initial release

2016

2009

1993

2014

2020

Current release

1703

3.10.0, March 2022

3.4-12

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

GPLv2, extended commercial license available

commercial

Open Source

GPL V3

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

C++

Server operating systems

Linux

All OS with a Java VM

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

hosted

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

with some exceptions

yes

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

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

SQL-like query language

APIs and other access methods

LDAP

JCache

CLI Client
JDBC
ODBC

Proprietary protocol
Thrift

Supported programming languages

All languages with LDAP bindings

Java

.Net
Basic
C
Java
Objective C
PHP
Python

JavaScript (Node.js)
Python

C++

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Cache Event Listeners

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

by using Terracotta Server

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

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

Tunable Consistency (Strong, Eventual, Weak)

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

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

Access rights can be defined down to the item level

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.