DBMS > Manticore Search vs. OrigoDB vs. RocksDB vs. Splunk

System Properties Comparison Manticore Search vs. OrigoDB vs. RocksDB vs. Splunk

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Analytics Platform for Big Data

Primary database model

Search engine

Document store
Object oriented DBMS

Key-value store

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.23
Rank	#317	Overall
	#21	Search engines

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	88.71
Rank	#14	Overall
	#2	Search engines

Website

Technical documentation

manual.manticoresearch.com

origodb.com/docs

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

Manticore Software

Robert Friberg et al

Facebook, Inc.

Splunk Inc.

Initial release

2017

2009

under the name LiveDB

2013

2003

Current release

6.0, February 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

GPL version 2

Open Source

BSD

commercial

Limited free edition and free developer edition available

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

Linux

Linux
OS X
Solaris
Windows

Data scheme

Fixed schema

yes

schema-free

yes

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

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

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

Splunk Search Processing Language for search commands

APIs and other access methods

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

.NET Client API
HTTP API
LINQ

C++ API
Java API

HTTP REST

Supported programming languages

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

.Net

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Domain Events

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

client side managed; servers are not synchronized

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

Source-replica replication

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual 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

yes

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

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.