DBMS > Apache Impala vs. GeoMesa vs. IBM Db2 Event Store vs. PostGIS

System Properties Comparison Apache Impala vs. GeoMesa vs. IBM Db2 Event Store vs. PostGIS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

Distributed Event Store optimized for Internet of Things use cases

Spatial extension of PostgreSQL

Primary database model

Relational DBMS

Spatial DBMS

Event Store
Time Series DBMS

Spatial DBMS

Secondary database models

Document store

Relational DBMS

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.27
Rank	#309	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Website

impala.apache.org

www.geomesa.org

www.ibm.com/products/db2-event-store

postgis.net

Technical documentation

impala.apache.org/impala-docs.html

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

www.ibm.com/docs/en/db2-event-store

postgis.net/documentation

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

CCRi and others

IBM

Initial release

2013

2014

2017

2005

Current release

4.1.0, June 2022

5.0.0, May 2024

2.0

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache License 2.0

commercial

free developer edition available

Open Source

GPL v2.0

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++

Scala

C and C++

Server operating systems

Linux

Linux, macOS, Windows for the developer addition

Data scheme

yes

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

through the embedded Spark runtime

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

depending on storage layer

Active-active shard replication

yes

based on PostgreSQL

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

yes

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

yes

based on PostgreSQL

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

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

Advancements in streaming data storage, real-time analysis and machine learning
25 July 2019, IBM

How IBM Is Turning Db2 into an 'AI Database'
3 June 2019, Datanami

Best cloud databases of 2022
4 October 2022, ITPro

Why a robust data management strategy is essential today | IBM HDM
19 September 2019, Express Computer

provided by Google News

Share this page