DBMS > DataFS vs. GeoMesa vs. KairosDB vs. Manticore Search

System Properties Comparison DataFS vs. GeoMesa vs. KairosDB vs. Manticore Search

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

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

Distributed Time Series DBMS based on Cassandra or H2

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

Primary database model

Secondary database models

Graph DBMS

Time Series DBMS

using the Manticore Columnar Library

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

Score	0.09
Rank	#360	Overall
	#17	Object oriented DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Website

newdatabase.com

www.geomesa.org

github.com/kairosdb/kairosdb

manticoresearch.com

Technical documentation

dev.mobiland.com/Overview.xsp

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

kairosdb.github.io

manual.manticoresearch.com

Developer

Mobiland AG

CCRi and others

Manticore Software

Initial release

2018

2014

2013

2017

Current release

1.1.263, October 2022

5.0.0, May 2024

1.2.2, November 2018

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

GPL 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

Java

C++

Server operating systems

Windows

Linux
OS X
Windows

FreeBSD
Linux
macOS
Windows

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

yes

schema-free

Fixed schema

Typing

predefined data types such as float or date

yes

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

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

SQL

Support of SQL

SQL-like query language

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

Graphite protocol
HTTP REST
Telnet API

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

Supported programming languages

.Net
C
C#
C++
VB.Net

Java
JavaScript

Node.js
PHP
Python

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

Server-side scripts

Stored procedures

user defined functions

Triggers

no, except callback-events from server when changes happened

Partitioning methods

Methods for storing different data on different nodes

Proprietary Sharding system

depending on storage layer

Sharding

based on Cassandra

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

selectable replication factor

based on Cassandra

Synchronous replication based on Galera library

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

yes

Transaction concepts

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

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.

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

Windows-Profile

yes

depending on the DBMS used for storage

simple password-based access control

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

Recent citations in the news

Real-Time Performance and Health Monitoring Using Netdata
2 September 2019, CNX Software

provided by Google 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

Share this page