DBMS > Drizzle vs. GeoMesa vs. H2 vs. Manticore Search

System Properties Comparison Drizzle vs. GeoMesa vs. H2 vs. Manticore Search

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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

Primary database model

Secondary database models

Spatial DBMS

Time Series DBMS

using the Manticore Columnar Library

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Website

www.geomesa.org

www.h2database.com

manticoresearch.com

Technical documentation

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

www.h2database.com/html/main.html

manual.manticoresearch.com

Developer

Drizzle project, originally started by Brian Aker

CCRi and others

Thomas Mueller

Manticore Software

Initial release

2008

2014

2005

2017

Current release

7.2.4, September 2012

5.0.0, May 2024

2.2.220, July 2023

6.0, February 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache License 2.0

Open Source

dual-licence (Mozilla public license, Eclipse public license)

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

C++

Scala

Java

C++

Server operating systems

FreeBSD
Linux
OS X

All OS with a Java VM

FreeBSD
Linux
macOS
Windows

Data scheme

yes

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

yes

with proprietary extensions

yes

SQL-like query language

APIs and other access methods

JDBC

JDBC
ODBC

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

Supported programming languages

C
C++
Java
PHP

Java

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

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

depending on storage layer

With clustering: 2 database servers on different computers operate on identical copies of a database

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

depending on storage layer

Immediate Consistency

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

yes, multi-version concurrency control (MVCC)

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

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

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

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Spatial database management systems
6 April 2021, 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

8 Powerful Alternatives to Elasticsearch
25 April 2024, Insider Monkey

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

provided by Google News

Share this page