DBMS > GeoMesa vs. GigaSpaces vs. IBM Db2 warehouse vs. Microsoft Azure Cosmos DB

System Properties Comparison GeoMesa vs. GigaSpaces vs. IBM Db2 warehouse vs. Microsoft Azure Cosmos DB

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

Cloud-based data warehousing service

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Spatial DBMS

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Graph DBMS
Search engine

Spatial DBMS

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.37
Rank	#160	Overall
	#74	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

www.geomesa.org

www.gigaspaces.com

www.ibm.com/products/db2/warehouse

azure.microsoft.com/services/cosmos-db

Technical documentation

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

docs.gigaspaces.com/latest/landing.html

learn.microsoft.com/azure/cosmos-db

Developer

CCRi and others

Gigaspaces Technologies

IBM

Microsoft

Initial release

2014

2000

2014

Current release

5.0.0, May 2024

15.5, September 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2; Commercial licenses available

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

Java, C++, .Net

Server operating systems

Linux
macOS
Solaris
Windows

hosted

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

Import/export of XML data possible

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL-99 for query and DML statements

yes

SQL-like query language

APIs and other access methods

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

.NET Client API
JDBC
ODBC
OLE DB

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

.Net
C++
Java
Python
Scala

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

PL/SQL, SQL PL

JavaScript

Triggers

yes, event driven architecture

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

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

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.