DBMS > Manticore Search vs. OrigoDB vs. Prometheus vs. searchxml

System Properties Comparison Manticore Search vs. OrigoDB vs. Prometheus vs. searchxml

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.

A fully ACID in-memory object graph database

Open-source Time Series DBMS and monitoring system

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Search engine

Document store
Object oriented DBMS

Time Series DBMS

Native XML DBMS
Search engine

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.22
Rank	#312	Overall
	#21	Search engines

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

manticoresearch.com

origodb.com

prometheus.io

www.searchxml.net/category/products

Technical documentation

manual.manticoresearch.com

origodb.com/docs

prometheus.io/docs

www.searchxml.net/support/handouts

Developer

Manticore Software

Robert Friberg et al

informationpartners gmbh

Initial release

2017

2009

under the name LiveDB

2015

Current release

6.0, February 2023

1.0

License

Commercial or Open Source

Open Source

GPL version 2

Open Source

Apache 2.0

commercial

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

Server operating systems

FreeBSD
Linux
macOS
Windows

Linux
Windows

Windows

Data scheme

Fixed schema

yes

schema-free

Typing

predefined data types such as float or date

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

User defined using .NET types and collections

Numeric data only

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

can be achieved using .NET

Import of XML data possible

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

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

.NET Client API
HTTP API
LINQ

RESTful HTTP/JSON API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

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

.Net

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

user defined functions

yes

on the application server

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

horizontal partitioning

client side managed; servers are not synchronized

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

Source-replica replication

yes

by Federation

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

multiple readers, single writer

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

Write ahead log

yes

In-memory capabilities

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

yes

User concepts

Access control

Role based authorization

Domain, group and role-based access control at the document level and for application services

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

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

Apex Legends hacker says game developers patched exploit used on streamers
25 April 2024, Yahoo News Canada

provided by Google News

VTEX scales to 150 million metrics using Amazon Managed Service for Prometheus | Amazon Web Services
10 March 2024, AWS Blog

VictoriaMetrics Offers Prometheus Replacement for Time Series Monitoring
17 July 2023, The New Stack

Linux System Monitoring with Prometheus, Grafana, and collectd
1 February 2024, Linux Journal

Consider Grafana vs. Prometheus for your time-series tools
18 October 2021, TechTarget

How to reduce Istio sidecar metric cardinality with Amazon Managed Service for Prometheus | Amazon Web Services
10 October 2023, AWS Blog

provided by Google News

Share this page