DBMS > GeoMesa vs. Greenplum vs. Microsoft Azure AI Search vs. Microsoft Azure Cosmos DB

System Properties Comparison GeoMesa vs. Greenplum vs. Microsoft Azure AI Search 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.

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Search-as-a-service for web and mobile app development

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Spatial DBMS

Relational DBMS

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store
Spatial DBMS

Vector DBMS

Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	5.52
Rank	#59	Overall
	#6	Search engines

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

Website

www.geomesa.org

greenplum.org

azure.microsoft.com/en-us/services/search

azure.microsoft.com/services/cosmos-db

Technical documentation

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

docs.greenplum.org

learn.microsoft.com/en-us/azure/search

learn.microsoft.com/azure/cosmos-db

Developer

CCRi and others

Pivotal Software Inc.

Microsoft

Initial release

2014

2005

2015

2014

Current release

5.0.0, May 2024

7.0.0, September 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

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

Server operating systems

Linux

hosted

Data scheme

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.

yes

since Version 4.2

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

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

Supported programming languages

C
Java
Perl
Python
R

C#
Java
JavaScript
Python

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

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

yes

Implicit feature of the cloud service

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

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

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

yes

using Azure authentication

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.