DBMS > GridGain vs. Heroic vs. NSDb vs. RocksDB vs. SAP SQL Anywhere

System Properties Comparison GridGain vs. Heroic vs. NSDb vs. RocksDB vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Key-value store

Relational 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.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

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

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

www.gridgain.com

github.com/spotify/heroic

nsdb.io

rocksdb.org

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

www.gridgain.com/docs/index.html

spotify.github.io/heroic

nsdb.io/Architecture

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

Developer

GridGain Systems, Inc.

Spotify

Facebook, Inc.

SAP

formerly Sybase

Initial release

2007

2014

2017

2013

1992

Current release

GridGain 8.5.1

9.2.1, May 2024

17, July 2015

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Open Source

BSD

commercial

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

Java

Java, Scala

C++

Server operating systems

Linux
OS X
Solaris
Windows

Linux
macOS

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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 Elasticsearch

all fields are automatically indexed

yes

SQL

Support of SQL

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

SQL-like query language

yes

APIs and other access methods

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

gRPC
HTTP REST
WebSocket

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Java
Scala

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

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

yes, in C/C++, Java, .Net or Perl

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

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

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.