DBMS > Manticore Search vs. MySQL vs. Postgres-XL vs. TerminusDB

System Properties Comparison Manticore Search vs. MySQL vs. Postgres-XL vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used open source RDBMS

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Search engine

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Graph DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Spatial DBMS

Document store
RDF store

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

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

Technical documentation

manual.manticoresearch.com

dev.mysql.com/doc

www.postgres-xl.org/documentation

terminusdb.github.io/terminusdb/#

Developer

Manticore Software

Oracle

since 2010, originally MySQL AB, then Sun

DataChemist Ltd.

Initial release

2017

1995

2014

since 2012, originally named StormDB

2018

Current release

6.0, February 2023

8.4.0, April 2024

10 R1, October 2018

11.0.0, January 2023

License

Commercial or Open Source

Open Source

GPL version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Mozilla public license

Open Source

GPL V3

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

Prolog, Rust

Server operating systems

FreeBSD
Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS

Linux

Data scheme

Fixed schema

yes

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

XML type, but no XML query functionality

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

yes

distributed, parallel query execution

SQL-like query language (WOQL)

APIs and other access methods

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

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

Multi-source replication
Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

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

not for MyISAM storage engine

ACID

MVCC

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 journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

Role-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.