DBMS > GridGain vs. PouchDB vs. RocksDB vs. VoltDB

System Properties Comparison GridGain vs. PouchDB vs. RocksDB vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GridGain is an in-memory computing platform, built on Apache Ignite

JavaScript DBMS with an API inspired by CouchDB

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Key-value store
Relational DBMS

Document store

Key-value store

Relational DBMS

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

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

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

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

Technical documentation

www.gridgain.com/docs/index.html

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

docs.voltdb.com

Developer

GridGain Systems, Inc.

Apache Software Foundation

Facebook, Inc.

VoltDB Inc.

Initial release

2007

2012

2013

2010

Current release

GridGain 8.5.1

7.1.1, June 2019

8.11.4, April 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

Linux
OS X
Solaris
Windows

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

Linux

Linux
OS X

for development

Data scheme

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.

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

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

yes

only a subset of SQL 99

APIs and other access methods

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

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

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

View functions in JavaScript

Java

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

Snapshots and command logging

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

Users and roles with access to stored procedures

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.