DBMS > GridGain vs. HarperDB vs. RocksDB vs. Solr

System Properties Comparison GridGain vs. HarperDB vs. RocksDB vs. Solr

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

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

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Key-value store
Relational DBMS

Document store

Key-value store

Search engine

Secondary database models

Spatial DBMS

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

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	0.60
Rank	#244	Overall
	#38	Document stores

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

Score	41.02
Rank	#24	Overall
	#3	Search engines

Website

Technical documentation

www.gridgain.com/docs/index.html

docs.harperdb.io/docs

github.com/facebook/rocksdb/wiki

solr.apache.org/resources.html

Developer

GridGain Systems, Inc.

HarperDB

Facebook, Inc.

Apache Software Foundation

Initial release

2007

2017

2013

2006

Current release

GridGain 8.5.1

3.1, August 2021

9.2.1, May 2024

9.6.1, May 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

BSD

Open Source

Apache Version 2

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

Node.js

C++

Java

Server operating systems

Linux
OS X
Solaris
Windows

Linux
OS X

Linux

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

dynamic schema

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

JSON data types

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

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

SQL-like data manipulation statements

Solr Parallel SQL Interface

APIs and other access methods

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

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

C++ API
Java API

Java API
RESTful HTTP/JSON API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

C
C++
Go
Java
Perl
Python
Ruby

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

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

Custom Functions

since release 3.1

Java plugins

Triggers

yes (cache interceptors and events)

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

A table resides as a whole on one (or more) nodes in a cluster

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

the nodes on which a table resides can be defined

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

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

Atomic execution of specific operations

yes

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

Access rights for users and roles

yes

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.