DBMS > Drizzle vs. EJDB vs. Manticore Search vs. Newts

System Properties Comparison Drizzle vs. EJDB vs. Manticore Search vs. Newts

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.

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Time Series DBMS based on Cassandra

Primary database model

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.10
Rank	#314	Overall
	#41	Document stores

Score	0.07
Rank	#326	Overall
	#20	Search engines

Score	0.00
Rank	#354	Overall
	#33	Time Series DBMS

Website

ejdb.org

manticoresearch.com

opennms.github.io/newts

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

manual.manticoresearch.com

github.com/OpenNMS/newts/wiki

Developer

Drizzle project, originally started by Brian Aker

Softmotions

Manticore Software

OpenNMS Group

Initial release

2008

2012

2017

2014

Current release

7.2.4, September 2012

4.2, December 2021

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

GPLv2

Open Source

GPL version 2

Open Source

Apache 2.0

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++

Java

Server operating systems

FreeBSD
Linux
OS X

server-less

FreeBSD
Linux
macOS
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

JDBC

in-process shared library

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

HTTP REST
Java API

Supported programming languages

C
C++
Java
PHP

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

Java

Server-side scripts

Stored procedures

user defined functions

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

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

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Synchronous replication based on Galera library

selectable replication factor

based on Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

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.

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

Recent citations in the news

Build A Web Crawler with Search bar Using Wget and Manticore [A Step By Step Guide]
18 April 2020, hackernoon.com

How To Develop Your Custom Autocorrect Implementation with Manticore [A Step by Step Guide]
20 February 2020, hackernoon.com

Highlighting in Search Results
24 May 2020, hackernoon.com

provided by Google News

Share this page