DBMS > GeoMesa vs. GridGain vs. IBM Db2 Event Store vs. OrigoDB

System Properties Comparison GeoMesa vs. GridGain vs. IBM Db2 Event Store vs. OrigoDB

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.

GridGain is an in-memory computing platform, built on Apache Ignite

Distributed Event Store optimized for Internet of Things use cases

A fully ACID in-memory object graph database

Primary database model

Spatial DBMS

Key-value store
Relational DBMS

Event Store
Time Series DBMS

Document store
Object oriented DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	0.19
Rank	#323	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

www.geomesa.org

www.gridgain.com

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

origodb.com

Technical documentation

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

www.gridgain.com/docs/index.html

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

origodb.com/docs

Developer

CCRi and others

GridGain Systems, Inc.

IBM

Robert Friberg et al

Initial release

2014

2007

2017

2009

under the name LiveDB

Current release

4.0.5, February 2024

GridGain 8.5.1

2.0

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free developer edition available

Open Source

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++, .Net

C and C++

Server operating systems

Linux
OS X
Solaris
Windows

Linux

Linux, macOS, Windows for the developer addition

Linux
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

through the embedded Spark runtime

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

.NET Client API
HTTP API
LINQ

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

.Net

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

yes

Triggers

yes (cache interceptors and events)

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes (replicated cache)

Active-active shard replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes

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

yes

Write ahead log

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

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

Role based authorization

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

GridGain's 2023 Growth Positions Company for Strong 2024
25 January 2024, Datanami

GridGain in-memory data and generative AI – Blocks and Files
10 May 2024, Blocks & Files

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain Adds Andy Sacks as Chief Revenue Officer, Promotes Lalit Ahuja to Chief Customer and Product Officer ...
17 July 2023, Yahoo Finance

GridGain: Product Overview and Analysis
5 June 2019, eWeek

provided by Google News

The vision for Db2
26 February 2019, biplatform.nl

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

IBM Builds New Ultra-Fast Platform for Hoovering Up and Analyzing Data from Anywhere
31 May 2018, Data Center Knowledge

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