DBMS > GridDB vs. Heroic vs. Percona Server for MongoDB vs. SAP HANA

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable in-memory time series database optimized for IoT and Big Data

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

Primary database model

Time Series DBMS

Document store

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

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.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

griddb.net

github.com/spotify/heroic

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

www.sap.com/products/hana.html

Technical documentation

docs.griddb.net

spotify.github.io/heroic

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

help.sap.com/hana

Developer

Toshiba Corporation

Spotify

Percona

SAP

Initial release

2013

2014

2015

2010

Current release

5.1, August 2022

3.4.10-2.10, November 2017

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

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

C++

Java

C++

Server operating systems

Linux

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

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

proprietary protocol using JSON

JDBC
ODBC

Supported programming languages

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

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

Server-side scripts

Stored procedures

JavaScript

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

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 at container level

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

Access rights for users can be defined per database

Access rights for users and roles

yes

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.