DBMS > Apache Drill vs. CouchDB vs. GeoMesa vs. OpenQM

System Properties Comparison Apache Drill vs. CouchDB vs. GeoMesa vs. OpenQM

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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

QpenQM is a high-performance, self-tuning, multi-value DBMS

Primary database model

Document store
Relational DBMS

Document store

Spatial DBMS

Multivalue DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	1.90
Rank	#126	Overall
	#23	Document stores
	#60	Relational DBMS

Score	7.46
Rank	#51	Overall
	#7	Document stores

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

Website

drill.apache.org

couchdb.apache.org

www.geomesa.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

Technical documentation

drill.apache.org/docs

docs.couchdb.org/en/stable

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

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

CCRi and others

Rocket Software, originally Martin Phillips

Initial release

2012

2005

2014

1993

Current release

1.20.3, January 2023

3.3.3, December 2023

5.0.1, July 2024

3.4-12

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache version 2

Open Source

Apache License 2.0

Open Source

GPLv2, extended 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

Erlang

Scala

Server operating systems

Linux
OS X
Windows

Android
BSD
Linux
OS X
Solaris
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

schema-free

yes

with some exceptions

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

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

Supported programming languages

C++

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

View functions in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

depending on storage layer

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

depending on storage layer

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

User concepts

Access control

Depending on the underlying data source

Access rights for users can be defined per database

yes

depending on the DBMS used for storage

Access rights can be defined down to the item level

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

Couchbase climbs up the DB-Engines Ranking, increasing its popularity by 10% every month
2 June 2014, Matthias Gelbmann

show all

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
27 September 2019, Towards Data Science

MapR Advances Support for Flexible and High Performance Analytics on JSON and S3 Data with Apache Drill
30 January 2019, Business Wire

Apache Drill Adds New Data Formats
28 March 2022, iProgrammer

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

provided by Google News

How to install the CouchDB NoSQL database on Debian Server 11
16 June 2022, TechRepublic

IBM Cloudant pulls plan to fund new foundational layer for CouchDB
15 March 2022, The Register

Database Ransom Attacks Hit CouchDB and Hadoop Servers
18 January 2017, BleepingComputer

Hadoop, CouchDB Next Targets in Wave of Database Attacks
20 January 2017, Threatpost

CouchDB 3.0 ends admin party era
27 February 2020, DevClass

provided by Google News

Share this page