DBMS > EXASOL vs. Geode vs. Manticore Search vs. PouchDB vs. RocksDB

System Properties Comparison EXASOL vs. Geode vs. Manticore Search vs. PouchDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

JavaScript DBMS with an API inspired by CouchDB

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

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	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	2.34
Rank	#112	Overall
	#21	Document stores

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

Website

Technical documentation

www.exasol.com/resources

geode.apache.org/docs

manual.manticoresearch.com

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

Developer

Exasol

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Manticore Software

Apache Software Foundation

Facebook, Inc.

Initial release

2000

2002

2017

2012

2013

Current release

1.1, February 2017

6.0, February 2023

7.1.1, June 2019

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

GPL 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

Java

C++

JavaScript

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

FreeBSD
Linux
macOS
Windows

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

Linux

Data scheme

yes

schema-free

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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

yes

SQL-like query language (OQL)

SQL-like query language

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

Java Client API
Memcached protocol
RESTful HTTP API

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

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

Supported programming languages

Java
Lua
Python
R

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

View functions in JavaScript

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

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

Multi-source replication

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

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

yes

isolated transactions for atomic changes and binary logging for safe writes

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, groups and roles according to SQL-standard

Access rights per client and object definable

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.