DBMS > Atos Standard Common Repository vs. Dragonfly vs. Oracle Berkeley DB

System Properties Comparison Atos Standard Common Repository vs. Dragonfly 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

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

Widely used in-process key-value store

Primary database model

Document store
Key-value store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

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

Score	0.41
Rank	#266	Overall
	#38	Key-value stores

Score	1.90
Rank	#127	Overall
	#22	Key-value stores
	#3	Native XML DBMS

Website

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

github.com/dragonflydb/dragonfly
www.dragonflydb.io

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

Technical documentation

www.dragonflydb.io/docs

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

Developer

Atos Convergence Creators

DragonflyDB team and community contributors

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2016

2023

1994

Current release

1703

1.0, March 2023

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

BSL 1.1

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

C++

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

Server operating systems

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

Schema and schema-less with LDAP views

scheme-free

schema-free

Typing

predefined data types such as float or date

optional

strings, hashes, lists, sets, sorted sets, bit arrays

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

APIs and other access methods

LDAP

Proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

All languages with LDAP bindings

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
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

Server-side scripts

Stored procedures

Lua

Triggers

yes

publish/subscribe channels provide some trigger functionality

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

Atomic execution of command blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

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

Password-based authentication

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

DragonflyDB Announces $21m in New Funding and General Availability
21 March 2023, Business Wire

Intel Linux Kernel Optimizations Show Huge Benefit For High Core Count Servers
29 March 2023, Phoronix

SFU Computing Science researchers receive 2022 ACM SIGMOD Research Highlight Award.
24 February 2023, Simon Fraser University News

AMD Ryzen 7000 Series Make For Compelling Budget Servers, Leading Performance & Value Over Xeon E
5 September 2023, Phoronix

Google Cloud Tau T2A Ampere Altra vs. T2D AMD EPYC Performance
21 September 2022, Phoronix

provided by Google News

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

Margo I. Seltzer
18 August 2020, Berkman Klein Center

What is NoSQL and How do NoSQL Databases Work?
28 February 2022, TechTarget

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

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

provided by Google News

Share this page