DBMS > BoltDB vs. GridGain vs. Oracle NoSQL vs. SAP HANA

System Properties Comparison BoltDB vs. GridGain vs. Oracle NoSQL vs. SAP HANA

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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Key-value store

Key-value store
Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.76
Rank	#224	Overall
	#32	Key-value stores

Score	1.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

Score	2.96
Rank	#103	Overall
	#18	Document stores
	#17	Key-value stores
	#52	Relational DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Website

github.com/boltdb/bolt

www.gridgain.com

www.oracle.com/database/nosql/technologies/nosql

www.sap.com/products/hana.html

Technical documentation

www.gridgain.com/docs/index.html

docs.oracle.com/en/database/other-databases/nosql-database/index.html

help.sap.com/hana

Developer

GridGain Systems, Inc.

Oracle

SAP

Initial release

2013

2007

2011

2010

Current release

GridGain 8.5.1

23.3, December 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, C++, .Net

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux
Solaris SPARC/x86

Appliance or cloud-service

Data scheme

schema-free

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

yes

optional

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

SQL

Support of SQL

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

SQL-like DML and DDL statements

yes

APIs and other access methods

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

RESTful HTTP API

JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

SQLScript, R

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes (replicated cache)

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

configurable

ACID within a storage node (=shard)

ACID

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

off heap cache

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.