DBMS > BoltDB vs. GridGain vs. Postgres-XL vs. RocksDB vs. Solr

System Properties Comparison BoltDB vs. GridGain vs. Postgres-XL vs. RocksDB vs. Solr

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Key-value store
Relational DBMS

Relational DBMS

Key-value store

Search engine

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

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

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

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

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

github.com/boltdb/bolt

Technical documentation

www.gridgain.com/docs/index.html

www.postgres-xl.org/documentation

github.com/facebook/rocksdb/wiki

solr.apache.org/resources.html

Developer

GridGain Systems, Inc.

Facebook, Inc.

Apache Software Foundation

Initial release

2013

2007

2014

since 2012, originally named StormDB

2013

2006

Current release

GridGain 8.5.1

10 R1, October 2018

9.2.1, May 2024

9.6.0, April 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Mozilla public license

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

C++

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux
macOS

Linux

All OS with a Java VM

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

Data scheme

schema-free

yes

schema-free

yes

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

Typing

predefined data types such as float or date

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

XML type, but no XML query functionality

yes

Secondary indexes

yes

All search fields are automatically indexed

SQL

Support of SQL

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

yes

distributed, parallel query execution

Solr Parallel SQL Interface

APIs and other access methods

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

C++ API
Java API

Java API
RESTful HTTP/JSON API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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)

user defined functions

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

none

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes (replicated cache)

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

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

MVCC

yes

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

fine grained access rights according to SQL-standard

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.