DBMS > Manticore Search vs. MarkLogic vs. MySQL vs. RavenDB vs. Stardog

System Properties Comparison Manticore Search vs. MarkLogic vs. MySQL vs. RavenDB vs. Stardog

Editorial information provided by DB-Engines

Name

Description

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

Operational and transactional Enterprise NoSQL database

Widely used open source RDBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

Search engine

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Key/Value like access via memcached API

Document store

Graph DBMS
RDF store

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.23
Rank	#301	Overall
	#21	Search engines

Score	4.15
Rank	#70	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#8	Search engines

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	2.68
Rank	#102	Overall
	#19	Document stores

Score	1.93
Rank	#121	Overall
	#10	Graph DBMS
	#6	RDF stores

Website

manticoresearch.com

www.progress.com/marklogic

www.mysql.com

ravendb.net

www.stardog.com

Technical documentation

manual.manticoresearch.com

www.progress.com/marklogic/documentation

dev.mysql.com/doc

ravendb.net/docs

docs.stardog.com

Developer

Manticore Software

MarkLogic Corp.

Oracle

since 2010, originally MySQL AB, then Sun

Hibernating Rhinos

Stardog-Union

Initial release

2017

2001

1995

2010

Current release

6.0, February 2023

11.0, December 2022

9.0.0, July 2024

5.4, July 2022

7.3.0, May 2020

License

Commercial or Open Source

Open Source

GPL version 2

commercial

restricted free version is available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL version 3, commercial license available

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

C and C++

Java

Server operating systems

FreeBSD
Linux
macOS
Windows

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

Linux
macOS
Windows

Data scheme

Fixed schema

schema-free

Schema can be enforced

yes

schema-free

schema-free and OWL/RDFS-schema support

Typing

predefined data types such as float or date

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

yes

Import/export of XML data possible

Secondary indexes

yes

full-text index on all search fields

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

SQL-like query language

yes

SQL92

yes

with proprietary extensions

SQL-like query language (RQL)

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

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

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

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

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

via XQuery or JavaScript

yes

proprietary syntax

yes

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

yes

Multi-source replication
Source-replica replication

Multi-source replication

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

relationships 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

can act as a resource manager in an XA/JTA transaction

ACID

not for MyISAM storage engine

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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, with Range Indexes

yes

User concepts

Access control

Role-based access control at the document and subdocument levels

Users with fine-grained authorization concept

no user groups or roles

Authorization levels configured per client per database

Access rights for users and roles

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.