DBMS > Atos Standard Common Repository vs. EJDB vs. Linter vs. Oracle Berkeley DB vs. SWC-DB

System Properties Comparison Atos Standard Common Repository vs. EJDB vs. Linter vs. Oracle Berkeley DB vs. SWC-DB

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

RDBMS for high security requirements

Widely used in-process key-value store

A high performance, scalable Wide Column DBMS

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Wide column store

Secondary database models

Spatial DBMS

Time Series DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

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

github.com/Softmotions/ejdb

linter.ru

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

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

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

Developer

Atos Convergence Creators

Softmotions

relex.ru

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Alex Kashirin

Initial release

2016

2012

1990

1994

2020

Current release

1703

18.1.40, May 2020

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

GPLv2

commercial

Open Source

commercial license available

Open Source

GPL V3

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 and C++

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

C++

Server operating systems

Linux

server-less

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

schema-free

Typing

predefined data types such as float or date

optional

yes

string, integer, double, bool, date, object_id

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

yes

SQL interfaced based on SQLite is available

SQL-like query language

APIs and other access methods

LDAP

in-process shared library

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Proprietary protocol
Thrift

Supported programming languages

All languages with LDAP bindings

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

.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

C++

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

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

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

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

Read/Write Locking

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

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

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

Margo I. Seltzer | Berkman Klein Center
18 August 2020, Berkman Klein Center

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular -- ADTmag
5 March 2019, ADT Magazine

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

The importance of bitcoin nodes and how to start one
9 May 2014, The Merkle News

provided by Google News

2022 All O-Zone Football Team
17 December 2022, Ozarks Sports Zone

provided by Google News

Share this page