DBMS > Ignite vs. Manticore Search vs. PouchDB vs. RocksDB vs. STSdb

System Properties Comparison Ignite vs. Manticore Search vs. PouchDB vs. RocksDB vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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)

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Key-value store
Relational DBMS

Search engine

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	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

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

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Website

github.com/STSSoft/STSdb4

Technical documentation

apacheignite.readme.io/docs

manual.manticoresearch.com

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Manticore Software

Apache Software Foundation

Facebook, Inc.

STS Soft SC

Initial release

2015

2017

2012

2013

2011

Current release

Apache Ignite 2.6

6.0, February 2023

7.1.1, June 2019

9.2.1, May 2024

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2

Open Source

BSD

Open Source

GPLv2, commercial license 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

C++, Java, .Net

C++

JavaScript

C++

Server operating systems

Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Windows

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

Linux

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

primitive types and user defined types (classes)

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.

yes

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

via views

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

SQL-like query language

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

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

.NET Client API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

C#
Java

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

user defined functions

View functions in JavaScript

Triggers

yes (cache interceptors and events)

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Synchronous replication based on Galera library

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

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

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

Security Hooks for custom implementations

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.