DBMS > KeyDB vs. Manticore Search vs. PouchDB vs. SQLite

System Properties Comparison KeyDB vs. Manticore Search vs. PouchDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

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.71
Rank	#226	Overall
	#33	Key-value stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/Snapchat/KeyDB
keydb.dev

manticoresearch.com

pouchdb.com

www.sqlite.org

Technical documentation

docs.keydb.dev

manual.manticoresearch.com

pouchdb.com/guides

www.sqlite.org/docs.html

Developer

EQ Alpha Technology Ltd.

Manticore Software

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2019

2017

2012

2000

Current release

6.0, February 2023

7.1.1, June 2019

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

BSD-3

Open Source

GPL version 2

Open Source

Public Domain

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

JavaScript

Server operating systems

Linux

FreeBSD
Linux
macOS
Windows

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

server-less

Data scheme

schema-free

Fixed schema

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

yes

not rigid because of 'dynamic typing' concept.

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

by using the Redis Search module

yes

full-text index on all search fields

yes

via views

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

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

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

JavaScript

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Lua

user defined functions

View functions in JavaScript

Triggers

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Synchronous replication based on Galera library

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple password-based access control and ACL

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.