DBMS > GeoMesa vs. Manticore Search vs. OrientDB

System Properties Comparison GeoMesa vs. Manticore Search vs. OrientDB

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.

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

Multi-model DBMS (Document, Graph, Key/Value)

Primary database model

Spatial DBMS

Search engine

Document store
Graph DBMS
Key-value store

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Website

www.geomesa.org

manticoresearch.com

orientdb.org

Technical documentation

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

manual.manticoresearch.com

www.orientdb.com/docs/last/index.html

Developer

CCRi and others

Manticore Software

OrientDB LTD; CallidusCloud; SAP

Initial release

2014

2017

2010

Current release

5.0.0, May 2024

6.0, February 2023

3.2.29, March 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL version 2

Open Source

Apache version 2

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

C++

Java

Server operating systems

FreeBSD
Linux
macOS
Windows

All OS with a Java JDK (>= JDK 6)

Data scheme

yes

Fixed schema

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

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

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language, no joins

APIs and other access methods

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

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

Supported programming languages

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

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

Server-side scripts

Stored procedures

user defined functions

Java, Javascript

Triggers

Hooks

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Synchronous replication based on Galera library

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Foreign keys

Referential integrity

yes

relationship in graphs

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

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.

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users and roles; record level security configurable

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Graph DBMS increased their popularity by 500% within the last 2 years
3 March 2015, Paul Andlinger

Graph DBMSs are gaining in popularity faster than any other database category
21 January 2014, Matthias Gelbmann

show all

Recent citations in the news

Integrating Manticore Search with Apache Superset
8 August 2023, hackernoon.com

Clickhouse vs Elasticsearch vs Manticore Search Query Times With a 1.7B NYC Taxi Rides Benchmark
1 June 2022, hackernoon.com

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

8 Google Alternatives: How to Search Crypto, the Dark Web, More
1 February 2023, Gizmodo

Highlighting in Search Results
24 May 2020, hackernoon.com

provided by Google News

OrientDB: A Flexible and Scalable Multi-Model NoSQL DBMS
21 January 2022, Open Source For You

Comparing Graph Databases II. Part 2: ArangoDB, OrientDB, and… | by Sam Bell
20 September 2019, Towards Data Science

The 12 Best Graph Databases to Consider for 2024
22 October 2023, Solutions Review

ArangoDB raises $10 million for NoSQL database management
14 March 2019, VentureBeat

Introducing Gremlin The Graph Database
14 August 2013, iProgrammer

provided by Google News

Share this page