DBMS > Apache Drill vs. Atos Standard Common Repository vs. Heroic vs. Oracle Berkeley DB

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Widely used in-process key-value store

Primary database model

Document store
Relational DBMS

Document store
Key-value store

Time Series DBMS

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	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

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

Website

drill.apache.org

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

github.com/spotify/heroic

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

Technical documentation

drill.apache.org/docs

spotify.github.io/heroic

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

Developer

Apache Software Foundation

Atos Convergence Creators

Spotify

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2012

2016

2014

1994

Current release

1.20.3, January 2023

1703

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache 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

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

Server operating systems

Linux
OS X
Windows

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

schema-free

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

yes

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

via Elasticsearch

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

LDAP

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Supported programming languages

C++

All languages with LDAP bindings

.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

user defined functions

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

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

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
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

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

LDAP bind 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

Apache Drill case study: A tutorial on processing CSV files
9 June 2016, TheServerSide.com

Analyse Kafka messages with SQL queries using Apache Drill
23 September 2019, Towards Data Science

Apache Drill improves big data SQL query engine
31 August 2021, TechTarget

Apache Drill Eliminates ETL, Data Transformation for MapR Database
11 April 2016, The New Stack

Apache Drill Poised to Crack Tough Data Challenges
19 May 2015, Datanami

provided by Google News

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

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

EC will investigate the Oracle/Sun takeover due to concerns about MySQL
3 September 2009, The Guardian

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

A Quick Look at Open Source Databases for Mobile App Development
29 April 2018, Open Source For You

provided by Google News

Share this page