DBMS > Atos Standard Common Repository vs. Ehcache vs. GeoSpock vs. Microsoft Access vs. SQLite

System Properties Comparison Atos Standard Common Repository vs. Ehcache vs. GeoSpock vs. Microsoft Access vs. SQLite

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

GeoSpock seems to be discontinued. Therefore it will be excluded 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

Spatial and temporal data processing engine for extreme data scale

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

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

www.ehcache.org

geospock.com

www.microsoft.com/en-us/microsoft-365/access

www.sqlite.org

Technical documentation

www.ehcache.org/documentation

developer.microsoft.com/en-us/access

www.sqlite.org/docs.html

Developer

Atos Convergence Creators

Terracotta Inc, owned by Software AG

GeoSpock

Microsoft

Dwayne Richard Hipp

Initial release

2016

2009

1992

2000

Current release

1703

3.10.0, March 2022

2.0, September 2019

1902 (16.0.11328.20222), March 2019

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Bundled with Microsoft Office

Open Source

Public Domain

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

Java, Javascript

C++

Server operating systems

Linux

All OS with a Java VM

hosted

Windows

Not a real database server, but making use of DLLs

server-less

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

optional

yes

not rigid because of 'dynamic typing' concept.

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

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

but not compliant to any SQL standard

yes

SQL-92 is not fully supported

APIs and other access methods

LDAP

JCache

JDBC

ADO.NET
DAO
ODBC
OLE DB

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

All languages with LDAP bindings

Java

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Triggers

yes

Cache Event Listeners

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

by using Terracotta Server

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

none

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

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

but no files for transaction logging

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 for users can be defined per table

a simple user-level security was built in till version Access 2003

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.