DBMS > Apache Impala vs. CouchDB vs. GeoMesa vs. XTDB

System Properties Comparison Apache Impala vs. CouchDB vs. GeoMesa vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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.

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Document store

Spatial DBMS

using the Geocouch extension

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

Score	14.03
Rank	#40	Overall
	#24	Relational DBMS

Score	10.26
Rank	#45	Overall
	#7	Document stores

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.09
Rank	#351	Overall
	#47	Document stores

Website

impala.apache.org

couchdb.apache.org

www.geomesa.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

impala.apache.org/impala-docs.html

docs.couchdb.org/en/stable

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

www.xtdb.com/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Apache Software Foundation

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

CCRi and others

Juxt Ltd.

Initial release

2013

2005

2014

2019

Current release

4.1.0, June 2022

3.3.3, December 2023

4.0.5, February 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache version 2

Open Source

Apache License 2.0

Open Source

MIT License

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

C++

Erlang

Scala

Clojure

Server operating systems

Linux

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL-like DML and DDL statements

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC

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

Clojure
Java

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

depending on storage layer

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

depending on storage layer

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

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

depending on storage layer

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Access rights for users can be defined per database

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

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 Impala becomes Top-Level Project
28 November 2017, SDTimes.com

Cloudera Bringing Impala to AWS Cloud
28 November 2017, Datanami

Apache Doris just 'graduated': Why care about this SQL data warehouse
24 June 2022, InfoWorld

Hudi: Uber Engineering’s Incremental Processing Framework on Apache Hadoop
12 March 2017, Uber

Updates & Upserts in Hadoop Ecosystem with Apache Kudu
27 October 2017, KDnuggets

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

CouchDB 3.0 ends admin party era • DEVCLASS
27 February 2020, DevClass

CouchDB 3.0 puts safety first
27 February 2020, InfoWorld

How to Connect Your Flask App With CouchDB: A NoSQL Database - MUO
14 August 2021, MakeUseOf

provided by Google News

Share this page