DBMS > GeoMesa vs. HBase vs. SAP HANA vs. Sphinx vs. TimesTen

System Properties Comparison GeoMesa vs. HBase vs. SAP HANA vs. Sphinx vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

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

Open source search engine for searching in data from different sources, e.g. relational databases

In-Memory RDBMS compatible to Oracle

Primary database model

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	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

www.geomesa.org

hbase.apache.org

www.sap.com/products/hana.html

sphinxsearch.com

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

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

hbase.apache.org/book.html

help.sap.com/hana

sphinxsearch.com/docs

docs.oracle.com/database/timesten-18.1

Developer

CCRi and others

Apache Software Foundation

Apache top-level project, originally developed by Powerset

SAP

Sphinx Technologies Inc.

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2014

2008

2010

2001

1998

Current release

5.0.0, May 2024

2.3.4, January 2021

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache version 2

commercial

Open Source

GPL version 2, commercial licence available

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

Java

C++

Server operating systems

Linux
Unix
Windows

using Cygwin

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

schema-free, schema definition possible

yes

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

yes

APIs and other access methods

Java API
RESTful HTTP API
Thrift

JDBC
ODBC

Proprietary protocol

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

Coprocessors in Java

SQLScript, R

PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

yes

none

Multi-source replication
Source-replica replication

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 or Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

Single row ACID (across millions of columns)

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

yes

by means of logfiles and checkpoints

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

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

yes

fine grained access rights according to SQL-standard

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.