DBMS > GigaSpaces vs. LeanXcale vs. PouchDB vs. RocksDB vs. Sphinx

System Properties Comparison GigaSpaces vs. LeanXcale vs. PouchDB vs. RocksDB vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

JavaScript DBMS with an API inspired by CouchDB

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

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Document store
Object oriented DBMS

Values are user defined objects

Key-value store
Relational DBMS

Document store

Key-value store

Search engine

Secondary database models

Graph DBMS
Search engine

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

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

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

Technical documentation

docs.gigaspaces.com/latest/landing.html

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

Developer

Gigaspaces Technologies

LeanXcale

Apache Software Foundation

Facebook, Inc.

Sphinx Technologies Inc.

Initial release

2000

2015

2012

2013

2001

Current release

15.5, September 2020

7.1.1, June 2019

8.11.4, April 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2; Commercial licenses available

commercial

Open Source

BSD

Open Source

GPL version 2, commercial licence 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

Java, C++, .Net

JavaScript

C++

Server operating systems

Linux
macOS
Solaris
Windows

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

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

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.

XML can be used for describing objects metadata

Secondary indexes

yes

via views

yes

full-text index on all search fields

SQL

Support of SQL

SQL-99 for query and DML statements

yes

through Apache Derby

SQL-like query language (SphinxQL)

APIs and other access methods

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

Proprietary protocol

Supported programming languages

.Net
C++
Java
Python
Scala

C
Java
Scala

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

View functions in JavaScript

Triggers

yes, event driven architecture

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

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

Map-Reduce pattern can be built with XAP task executors

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Role-based access control

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.