DBMS > FatDB vs. GeoMesa vs. Hazelcast vs. IBM Db2 Event Store

System Properties Comparison FatDB vs. GeoMesa vs. Hazelcast vs. IBM Db2 Event Store

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

A widely adopted in-memory data grid

Distributed Event Store optimized for Internet of Things use cases

Primary database model

Document store
Key-value store

Spatial DBMS

Key-value store

Event Store
Time Series DBMS

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.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

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

Website

www.geomesa.org

hazelcast.com

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

Technical documentation

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

hazelcast.org/imdg/docs

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

Developer

FatCloud

CCRi and others

Hazelcast

IBM

Initial release

2012

2014

2008

2017

Current release

5.0.0, May 2024

5.3.6, November 2023

2.0

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

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

Scala

Java

C and C++

Server operating systems

Windows

All OS with a Java VM

Linux

Linux, macOS, Windows for the developer addition

Data scheme

schema-free

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

Via inetgration in SQL Server

SQL-like query language

yes

through the embedded Spark runtime

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

Supported programming languages

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

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

via applications

yes

Event Listeners, Executor Services

yes

Triggers

yes

via applications

yes

Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

depending on storage layer

yes

Replicated Map

Active-active shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

depending on storage layer

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

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

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

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

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

Can implement custom security layer via applications

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 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 5.4 real time data processing platform boosts AI and consistency
17 April 2024, VentureBeat

Real-Time Data Platform Hazelcast Introduces New Chief Technology Officer Adrian Soars
7 November 2023, Finovate

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

provided by Google News

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

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

Best cloud databases of 2022
4 October 2022, ITPro

provided by Google News

Share this page