DBMS > GeoMesa vs. Infobright vs. SAP HANA

System Properties Comparison GeoMesa vs. Infobright vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Spatial DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.geomesa.org

ignitetech.com/softwarelibrary/infobrightdb

www.sap.com/products/hana.html

Technical documentation

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

help.sap.com/hana

Developer

CCRi and others

Ignite Technologies Inc.; formerly InfoBright Inc.

SAP

Initial release

2014

2005

2010

Current release

4.0.5, February 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

Server operating systems

Linux
Windows

Appliance or cloud-service

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.

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

yes

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.