DBMS > Atos Standard Common Repository vs. BigObject vs. Ehcache vs. H2

System Properties Comparison Atos Standard Common Repository vs. BigObject vs. Ehcache vs. H2

Please select another system to include it in the comparison.

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

Analytic DBMS for real-time computations and queries

A widely adopted Java cache with tiered storage options

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Primary database model

Document store
Key-value store

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

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

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Website

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

bigobject.io

www.ehcache.org

www.h2database.com

Technical documentation

docs.bigobject.io

www.ehcache.org/documentation

www.h2database.com/html/main.html

Developer

Atos Convergence Creators

BigObject, Inc.

Terracotta Inc, owned by Software AG

Thomas Mueller

Initial release

2016

2015

2009

2005

Current release

1703

3.10.0, March 2022

2.2.220, July 2023

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache Version 2; commercial licenses available

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

All OS with a Java VM

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

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 DML and DDL statements

yes

APIs and other access methods

LDAP

fluentd
ODBC
RESTful HTTP API

JCache

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Java

Server-side scripts

Stored procedures

Lua

Java Stored Procedures and User-Defined Functions

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

by using Terracotta Server

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

by using Terracotta Server

With clustering: 2 database servers on different computers operate on identical copies of a database

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

none

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

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

Read/write lock on objects (tables, trees)

yes

yes, multi-version concurrency control (MVCC)

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

Migration From JBoss 5 to JBoss 7: All It Takes Is 11 Easy Steps
3 June 2021, hackernoon.com

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, DZone

provided by Google News

Share this page