DBMS > GridGain vs. Heroic vs. RocksDB vs. Yanza

System Properties Comparison GridGain vs. Heroic vs. RocksDB vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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

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

Time Series DBMS for IoT Applications

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Key-value store

Time Series 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	0.51
Rank	#255	Overall
	#21	Time Series DBMS

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

Website

www.gridgain.com

github.com/spotify/heroic

rocksdb.org

yanza.com

Technical documentation

www.gridgain.com/docs/index.html

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

Developer

GridGain Systems, Inc.

Spotify

Facebook, Inc.

Yanza

Initial release

2007

2014

2013

2015

Current release

GridGain 8.5.1

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java, C++, .Net

Java

C++

Server operating systems

Linux
OS X
Solaris
Windows

Linux

Windows

Data scheme

yes

schema-free

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 Elasticsearch

SQL

Support of SQL

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

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

C++ API
Java API

HTTP API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

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

Triggers

yes (cache interceptors and events)

yes

Timer and event based

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

none

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

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes

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

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.