DBMS > BoltDB vs. Manticore Search vs. RocksDB vs. Splunk vs. Warp 10

System Properties Comparison BoltDB vs. Manticore Search vs. RocksDB vs. Splunk vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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

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

Analytics Platform for Big Data

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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.76
Rank	#224	Overall
	#32	Key-value stores

Score	0.23
Rank	#317	Overall
	#21	Search engines

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

Score	88.71
Rank	#14	Overall
	#2	Search engines

Score	0.08
Rank	#358	Overall
	#35	Time Series DBMS

Website

github.com/boltdb/bolt

Technical documentation

manual.manticoresearch.com

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

www.warp10.io/content/02_Getting_started

Developer

Manticore Software

Facebook, Inc.

Splunk Inc.

SenX

Initial release

2013

2017

2013

2003

2015

Current release

6.0, February 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPL version 2

Open Source

BSD

commercial

Limited free edition and free developer edition available

Open Source

Apache License 2.0

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

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Windows

Linux

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

schema-free

Fixed schema

schema-free

yes

schema-free

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

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

C++ API
Java API

HTTP REST

HTTP API
Jupyter
WebSocket

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication based on Galera library

yes

Multi-source replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

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

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

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users and roles

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.