DBMS > Amazon DocumentDB vs. EXASOL vs. GeoSpock vs. Manticore Search vs. OpenSearch

System Properties Comparison Amazon DocumentDB vs. EXASOL vs. GeoSpock vs. Manticore Search vs. OpenSearch

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Spatial and temporal data processing engine for extreme data scale

Multi-storage database for search, including full-text search.

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

Primary database model

Document store

Relational DBMS

Search engine

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Vector DBMS

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	16.36
Rank	#37	Overall
	#4	Search engines

Website

aws.amazon.com/documentdb

www.exasol.com

geospock.com

manticoresearch.com

github.com/opensearch-project
opensearch.org

Technical documentation

aws.amazon.com/documentdb/resources

www.exasol.com/resources

manual.manticoresearch.com

opensearch.org/docs/latest

Developer

Exasol

GeoSpock

Manticore Software

Amazon Web Services

Initial release

2019

2000

2017

2021

Current release

2.0, September 2019

6.0, February 2023

2.5.0, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2

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.

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

Java, Javascript

C++

Java

Server operating systems

hosted

FreeBSD
Linux
macOS
Windows

All OS with a Java VM

Data scheme

schema-free

yes

Fixed schema

schema-free

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

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

yes

temporal, categorical

yes

full-text index on all search fields

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

SQL-like query language

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

.Net
JDBC
ODBC
WebSocket

JDBC

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

Java API
RESTful HTTP/JSON API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

Java
Lua
Python
R

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Automatic sharding

Sharding

Partitioning is done manually, search queries against distributed index is supported

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

Synchronous replication based on Galera library

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

Transaction concepts

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

Atomic single-document operations

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights for users and roles

Access rights for users, groups and roles according to SQL-standard

Access rights for users can be defined per table

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.