DBMS > EsgynDB vs. GeoMesa vs. Hazelcast vs. TimesTen

System Properties Comparison EsgynDB vs. GeoMesa vs. Hazelcast vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

A widely adopted in-memory data grid

An in-memory SQL relational database that delivers microsecond response and high throughput for OLTP applications. TimesTen can be deployed as a standalone database or as a cache to a backend Oracle database.

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	1.26
Rank	#164	Overall
	#75	Relational DBMS

Website

www.esgyn.cn

www.geomesa.org

hazelcast.com

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

Technical documentation

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

hazelcast.org/imdg/docs

docs.oracle.com/en/database/other-databases/timesten/index.html

Developer

Esgyn

CCRi and others

Hazelcast

Oracle

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

Initial release

2015

2014

2008

1998

Current release

5.0.1, July 2024

5.3.6, November 2023

Release 22.1

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

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

Scala

Java

Server operating systems

Linux

All OS with a Java VM

IBM AIX Power PC 64-bit
Linux arm64
Linux x86-64
Solaris SPARC 64
Solaris SPARC/x86
Solaris x86-64

Data scheme

yes

schema-free

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

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

ODBC
ODP.NET
Oracle Call Interface (OCI)
Pro*C/C++ programming interfaces
SQL and PL/SQL via JDBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

C
C++
Java
Node.js
PL/SQL
Python

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Event Listeners, Executor Services

PL/SQL

Triggers

yes

Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

depending on storage layer

yes

Replicated Map

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

Immediate Consistency

depending on storage layer

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

ACID

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Role-based access control

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.

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

Hazelcast 5.4 real time data processing platform boosts AI and consistency
17 April 2024, VentureBeat

Hazelcast Weaves Wider Logic Threads Through The Data Fabric
7 March 2024, Forbes

Hazelcast Showcases Real-Time Data Platform at 2024 Gartner Summit
15 May 2024, Datanami

Hazelcast appoints Anthony Griffin as Chief Architect -
11 June 2024, Enterprise Times

Hazelcast Versus Redis: A Practical Comparison
4 January 2024, Database Trends and Applications

provided by Google News

Oracle starts peddling Exalytics in-memory appliance
12 March 2012, The Register

SAP S&D Benchmark - The Intel Xeon E7-8800 v3 Review: The POWER8 Killer?
8 May 2015, AnandTech

provided by Google News

Share this page