DBMS > Apache Impala vs. EsgynDB vs. GeoMesa vs. HarperDB

System Properties Comparison Apache Impala vs. EsgynDB vs. GeoMesa vs. HarperDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Primary database model

Relational DBMS

Spatial DBMS

Document store

Secondary database models

Document store

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.60
Rank	#244	Overall
	#38	Document stores

Website

Technical documentation

impala.apache.org/impala-docs.html

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

docs.harperdb.io/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Esgyn

CCRi and others

HarperDB

Initial release

2013

2015

2014

2017

Current release

4.1.0, June 2022

5.0.0, May 2024

3.1, August 2021

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache License 2.0

commercial

free community edition 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

C++

C++, Java

Scala

Node.js

Server operating systems

Linux

Linux
OS X

Data scheme

yes

dynamic schema

Typing

predefined data types such as float or date

yes

JSON data types

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-like data manipulation statements

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/ADO.Net

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

Java Stored Procedures

Custom Functions

since release 3.1

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

A table resides as a whole on one (or more) nodes in a cluster

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication between multi datacenters

depending on storage layer

yes

the nodes on which a table resides can be defined

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

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Access rights for users and roles

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

Serent Capital invests in software firm HarperDB
12 June 2024, PE Hub

HarperDB Attracts Significant Growth Investment from Serent Capital
12 June 2024, Business Wire

HarperDB Receives Growth Investment from Serent Capital
12 June 2024, FinSMEs

Startups of the Year 2023: Meet HarperDB - A Database and Application Development Platform
22 June 2023, hackernoon.com

Jaxon Repp on HarperDB Distributed Database Platform
23 March 2022, InfoQ.com

provided by Google News

Share this page