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

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable relational database for web apps written in pure JavaScript

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

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.32
Rank	#290	Overall
	#132	Relational DBMS

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

Website

google.github.io/lovefield

manticoresearch.com

rocksdb.org

www.splunk.com

Technical documentation

github.com/google/lovefield/blob/master/docs/spec_index.md

manual.manticoresearch.com

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

Developer

Google

Manticore Software

Facebook, Inc.

Splunk Inc.

Initial release

2014

2017

2013

2003

Current release

2.1.12, February 2017

6.0, February 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

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

JavaScript

C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

FreeBSD
Linux
macOS
Windows

Linux

Linux
OS X
Solaris
Windows

Data scheme

yes

Fixed schema

schema-free

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

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

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

Supported programming languages

JavaScript

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

Triggers

Using read-only observers

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication based on Galera library

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

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

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, by using IndexedDB or the cloud service Firebase Realtime Database

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

using MemoryDB

yes

User concepts

Access control

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.