DBMS > Atos Standard Common Repository vs. Ehcache vs. LevelDB vs. MySQL

System Properties Comparison Atos Standard Common Repository vs. Ehcache vs. LevelDB vs. MySQL

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

A widely adopted Java cache with tiered storage options

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Widely used open source RDBMS

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	4.79
Rank	#66	Overall
	#8	Key-value stores

Score	2.33
Rank	#111	Overall
	#19	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

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

www.ehcache.org

github.com/google/leveldb

www.mysql.com

Technical documentation

www.ehcache.org/documentation

github.com/google/leveldb/blob/main/doc/index.md

dev.mysql.com/doc

Developer

Atos Convergence Creators

Terracotta Inc, owned by Software AG

Google

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

2009

2011

1995

Current release

1703

3.10.0, March 2022

1.23, February 2021

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

C++

C and C++

Server operating systems

Linux

All OS with a Java VM

Illumos
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

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

yes

with proprietary extensions

APIs and other access methods

LDAP

JCache

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages with LDAP bindings

Java

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

by using Terracotta Server

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

none

Multi-source replication
Source-replica replication

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

not for MyISAM storage engine

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

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

with automatic compression on writes

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

Users with fine-grained authorization concept

no user groups or roles

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.