DBMS > Atos Standard Common Repository vs. GeoMesa vs. Immudb vs. Oracle Berkeley DB

System Properties Comparison Atos Standard Common Repository vs. GeoMesa vs. Immudb vs. Oracle Berkeley DB

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Widely used in-process key-value store

Primary database model

Document store
Key-value store

Spatial DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Relational DBMS

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.24
Rank	#295	Overall
	#42	Key-value stores

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Website

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

www.geomesa.org

github.com/codenotary/immudb
immudb.io

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

docs.immudb.io

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Atos Convergence Creators

CCRi and others

Codenotary

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2016

2014

2020

1994

Current release

1703

5.0.1, July 2024

1.2.3, April 2022

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

Open Source

commercial license 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

Scala

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

Linux

BSD
Linux
macOS
Solaris
Windows
z/OS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

Schema and schema-less with LDAP views

yes

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

SQL-like syntax

yes

SQL interfaced based on SQLite is available

APIs and other access methods

LDAP

gRPC protocol
PostgreSQL wire protocol

Supported programming languages

All languages with LDAP bindings

.Net
Go
Java
JavaScript (Node.js)
Python

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

depending on storage layer

yes

User concepts

Access control

LDAP bind authentication

yes

depending on the DBMS used for storage

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

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

A Step by Step Guide to immudb — the open source immutable database
18 May 2020, hackernoon.com

immudb (immutable database) ‘tamper-proof’ database
14 December 2021, ComputerWeekly.com

ImmuDB and Codenotary: It's a database, but the company isn't
20 December 2021, ZDNet

How Open-Source Database immudb Plans to Handle All That Metaverse Data
10 October 2022, Acceleration Economy

Immudb: Open-source database, built on a zero trust model
17 December 2021, Help Net Security

provided by Google News

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

What is NoSQL (Not Only SQL database)?
28 February 2022, TechTarget

Margo I. Seltzer
18 August 2020, Berkman Klein Center

Oracle acquires Sleepycat for code
17 August 2016, East Bay Times

How to store financial market data for backtesting
26 January 2019, Towards Data Science

provided by Google News

Share this page