DBMS > Amazon DocumentDB vs. GeoMesa vs. Microsoft Azure Table Storage vs. OpenSearch

System Properties Comparison Amazon DocumentDB vs. GeoMesa vs. Microsoft Azure Table Storage vs. OpenSearch

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

A Wide Column Store for rapid development using massive semi-structured datasets

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Primary database model

Secondary database models

Vector DBMS

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	16.03
Rank	#37	Overall
	#4	Search engines

Website

aws.amazon.com/documentdb

www.geomesa.org

azure.microsoft.com/en-us/services/storage/tables

github.com/opensearch-project
opensearch.org

Technical documentation

aws.amazon.com/documentdb/resources

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

opensearch.org/docs/latest

Developer

CCRi and others

Microsoft

Amazon Web Services

Initial release

2019

2014

2012

2021

Current release

5.0.0, May 2024

2.5.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2.0

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.

STACKIT OpenSearch offers OpenSearch in a managed version in enterprise grade, 100% GDPR-compliant, for a wide range of applications like analytics, website search, offering scalability and fast data access.
Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

Scala

Java

Server operating systems

hosted

All OS with a Java VM

Data scheme

schema-free

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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.

Secondary indexes

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query language

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

RESTful HTTP API

Java API
RESTful HTTP/JSON API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

yes

Triggers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

depending on storage layer

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

Transaction concepts

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

Atomic single-document operations

optimistic locking

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

Access rights for users and roles

yes

depending on the DBMS used for storage

Access rights based on private key authentication or shared access signatures

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.