DBMS > Cachelot.io vs. Manticore Search vs. OrientDB vs. PouchDB vs. RocksDB

System Properties Comparison Cachelot.io vs. Manticore Search vs. OrientDB vs. PouchDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

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

Multi-model DBMS (Document, Graph, Key/Value)

JavaScript DBMS with an API inspired by CouchDB

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

Primary database model

Key-value store

Search engine

Document store
Graph DBMS
Key-value store

Document store

Key-value store

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.00
Rank	#383	Overall
	#60	Key-value stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

Technical documentation

manual.manticoresearch.com

www.orientdb.com/docs/last/index.html

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

Developer

Manticore Software

OrientDB LTD; CallidusCloud; SAP

Apache Software Foundation

Facebook, Inc.

Initial release

2015

2017

2010

2012

2013

Current release

6.0, February 2023

3.2.29, March 2024

7.1.1, June 2019

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Simplified BSD License

Open Source

GPL version 2

Open Source

Apache version 2

Open Source

BSD

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

JavaScript

C++

Server operating systems

FreeBSD
Linux
OS X

FreeBSD
Linux
macOS
Windows

All OS with a Java JDK (>= JDK 6)

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

Linux

Data scheme

schema-free

Fixed schema

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

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

Secondary indexes

yes

full-text index on all search fields

yes

via views

SQL

Support of SQL

SQL-like query language

SQL-like query language, no joins

APIs and other access methods

Memcached protocol

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

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

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

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Java, Javascript

View functions in JavaScript

Triggers

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication based on Galera library

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

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

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

by using IndexedDB, WebSQL or LevelDB as backend

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; record level security configurable

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.