DBMS > Apache Drill vs. GeoMesa vs. mSQL vs. Oracle Berkeley DB

System Properties Comparison Apache Drill vs. GeoMesa vs. mSQL vs. Oracle Berkeley DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used in-process key-value store

Primary database model

Document store
Relational DBMS

Spatial DBMS

Relational 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.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

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

Website

drill.apache.org

www.geomesa.org

hughestech.com.au/products/msql

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

Technical documentation

drill.apache.org/docs

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

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

Developer

Apache Software Foundation

CCRi and others

Hughes Technologies

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2012

2014

1994

Current release

1.20.3, January 2023

4.0.5, February 2024

4.4, October 2021

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache License 2.0

commercial

free licenses can be provided

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

Scala

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

Server operating systems

Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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 SELECT statement is SQL:2003 compliant

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

Supported programming languages

C++

C
C++
Delphi
Java
Perl
PHP
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

user defined functions

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

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

depending on storage layer

none

Foreign keys

Referential integrity

Transaction concepts

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

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

depending on storage layer

yes

User concepts

Access control

Depending on the underlying data source

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

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 Poised to Crack Tough Data Challenges
19 May 2015, Datanami

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

Drill Mines Diverse Data Sets, Google Style
20 May 2015, The Next Platform

provided by Google News

Higher Education PS rules out ghost students before PAC
29 November 2018, diggers.news

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

Share this page