DBMS > GridGain vs. Heroic vs. Percona Server for MongoDB vs. SAP HANA vs. Valentina Server

System Properties Comparison GridGain vs. Heroic vs. Percona Server for MongoDB vs. SAP HANA vs. Valentina Server

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

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

Object-relational database and reports server

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Document store

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	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

www.gridgain.com

github.com/spotify/heroic

www.percona.com/mongodb/software/percona-server-for-mongodb

www.sap.com/products/hana.html

www.valentina-db.net

Technical documentation

www.gridgain.com/docs/index.html

spotify.github.io/heroic

docs.percona.com/percona-distribution-for-mongodb

help.sap.com/hana

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

GridGain Systems, Inc.

Spotify

Percona

SAP

Paradigma Software

Initial release

2007

2014

2015

2010

1999

Current release

GridGain 8.5.1

3.4.10-2.10, November 2017

2.0 SPS07 (April 4, 2023), April 2023

5.7.5

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL Version 2

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

C++

Server operating systems

Linux
OS X
Solaris
Windows

Linux

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

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

yes

SQL

Support of SQL

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

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

proprietary protocol using JSON

JDBC
ODBC

ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

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

JavaScript

SQLScript, R

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

via In-Memory Engine

yes

User concepts

Access control

Security Hooks for custom implementations

Access rights for users and roles

yes

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.