DBMS > Elasticsearch vs. Manticore Search vs. PostgreSQL

System Properties Comparison Elasticsearch vs. Manticore Search vs. PostgreSQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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

Widely used open source RDBMS

Developed as objectoriented DBMS (Postgres), gradually enhanced with 'standards' like SQL

Primary database model

Search engine
Vector DBMS

Search engine

Relational DBMS

with object oriented extensions, e.g.: user defined types/functions and inheritance. Handling of key/value pairs with hstore module.

Secondary database models

Document store
Spatial DBMS

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

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

Score	123.81
Rank	#9	Overall
	#1	Search engines
	#1	Vector DBMS

Score	0.28
Rank	#283	Overall
	#21	Search engines

Score	674.32
Rank	#4	Overall
	#4	Relational DBMS

Website

www.elastic.co/elasticsearch

manticoresearch.com

www.postgresql.org

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

manual.manticoresearch.com

www.postgresql.org/docs

Developer

Elastic

Manticore Software

PostgreSQL Global Development Group

www.postgresql.org/developer

Initial release

2010

2017

1989

1989: Postgres, 1996: PostgreSQL

Current release

8.6, January 2023

6.0, February 2023

16.4, August 2024

License

Commercial or Open Source

Open Source

Elastic License

Open Source

GPL version 2

Open Source

BSD

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

Java

C++

Server operating systems

All OS with a Java VM

FreeBSD
Linux
macOS
Windows

FreeBSD
HP-UX
Linux
NetBSD
OpenBSD
OS X
Solaris
Unix
Windows

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

Fixed schema

yes

Typing

predefined data types such as float or date

yes

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

All search fields are automatically indexed

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

standard with numerous extensions

APIs and other access methods

Java API
RESTful HTTP/JSON API

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

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

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

yes

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

partitioning by range, list and (since PostgreSQL 11) by hash

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication based on Galera library

Source-replica replication

other methods possible by using 3rd party extensions

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency

Foreign keys

Referential integrity

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

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.

yes

In-memory capabilities

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

Memcached and Redis integration

User concepts

Access control

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.