DBMS > Manticore Search vs. RocksDB vs. VoltDB vs. Yaacomo

System Properties Comparison Manticore Search vs. RocksDB vs. VoltDB vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Search engine

Key-value store

Relational DBMS

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.29
Rank	#302	Overall
	#21	Search engines

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

manticoresearch.com

rocksdb.org

www.voltdb.com

yaacomo.com

Technical documentation

manual.manticoresearch.com

github.com/facebook/rocksdb/wiki

docs.voltdb.com

Developer

Manticore Software

Facebook, Inc.

VoltDB Inc.

Q2WEB GmbH

Initial release

2017

2013

2010

2009

Current release

6.0, February 2023

9.2.1, May 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

GPL version 2

Open Source

BSD

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

FreeBSD
Linux
macOS
Windows

Linux

Linux
OS X

for development

Android
Linux
Windows

Data scheme

Fixed schema

schema-free

yes

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

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

only a subset of SQL 99

yes

APIs and other access methods

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

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

Java

Triggers

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

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

yes

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

FOREIGN KEY constraints are not supported

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

yes

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

yes

Snapshots and command logging

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

Users and roles with access to stored procedures

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.