DBMS > GeoMesa vs. GigaSpaces vs. GridGain vs. RocksDB

System Properties Comparison GeoMesa vs. GigaSpaces vs. GridGain vs. RocksDB

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 performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Spatial DBMS

Document store
Object oriented DBMS

Values are user defined objects

Key-value store
Relational DBMS

Key-value store

Secondary database models

Graph DBMS
Search engine

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1.03
Rank	#188	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

Technical documentation

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

docs.gigaspaces.com/latest/landing.html

www.gridgain.com/docs/index.html

github.com/facebook/rocksdb/wiki

Developer

CCRi and others

Gigaspaces Technologies

GridGain Systems, Inc.

Facebook, Inc.

Initial release

2014

2000

2007

2013

Current release

5.0.0, May 2024

15.5, September 2020

GridGain 8.5.1

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2; Commercial licenses available

commercial

Open Source

BSD

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

Server operating systems

Linux
macOS
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

schema-free

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.

XML can be used for describing objects metadata

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-99 for query and DML statements

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

APIs and other access methods

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

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

C++ API
Java API

Supported programming languages

.Net
C++
Java
Python
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

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

Triggers

yes, event driven architecture

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes (replicated cache)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes

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

Role-based access control

Security Hooks for custom implementations

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.