DBMS > Atos Standard Common Repository vs. MySQL vs. Oracle vs. Oracle Berkeley DB vs. Solr

System Properties Comparison Atos Standard Common Repository vs. MySQL vs. Oracle vs. Oracle Berkeley DB vs. Solr

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

Widely used open source RDBMS

Widely used RDBMS

Widely used in-process key-value store

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Document store
Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Search engine

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Spatial DBMS

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

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	1234.27
Rank	#1	Overall
	#1	Relational DBMS

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	44.28
Rank	#24	Overall
	#3	Search engines

Website

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

www.mysql.com

www.oracle.com/database

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

solr.apache.org

Technical documentation

dev.mysql.com/doc

docs.oracle.com/en/database

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

solr.apache.org/resources.html

Developer

Atos Convergence Creators

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Apache Software Foundation

Initial release

2016

1995

1980

1994

2006

Current release

1703

8.3.0, January 2024

23c, September 2023

18.1.40, May 2020

9.5.0, February 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

restricted free version is available

Open Source

commercial license available

Open Source

Apache Version 2

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

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

Java

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

Schema and schema-less with LDAP views

yes

Schemaless in JSON and XML columns

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

optional

yes

supports customizable data types and automatic typing

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

yes

Secondary indexes

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

Solr Parallel SQL Interface

APIs and other access methods

LDAP

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Java API
RESTful HTTP/JSON API

Supported programming languages

All languages with LDAP bindings

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

proprietary syntax

PL/SQL

also stored procedures in Java possible

Java plugins

Triggers

yes

only for the SQL API

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding, horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

not for MyISAM storage engine

ACID

isolation level can be parameterized

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

LDAP bind authentication

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

yes

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.