DBMS > GridGain vs. Heroic vs. SAP HANA vs. TypeDB

System Properties Comparison GridGain vs. Heroic vs. SAP HANA vs. TypeDB

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

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

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

TypeDB is a strongly-typed database with a rich and logical type system and TypeQL as its query language

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Relational DBMS

Graph DBMS
Relational DBMS

Often described as a 'hyper-relational' database, since it implements the 'Entity-Relationship Paradigm' to manage complex data structures and ontologies.

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.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.65
Rank	#234	Overall
	#20	Graph DBMS
	#107	Relational DBMS

Website

www.gridgain.com

github.com/spotify/heroic

www.sap.com/products/hana.html

typedb.com

Technical documentation

www.gridgain.com/docs/index.html

spotify.github.io/heroic

help.sap.com/hana

typedb.com/docs

Developer

GridGain Systems, Inc.

Spotify

SAP

Vaticle

Initial release

2007

2014

2010

2016

Current release

GridGain 8.5.1

2.0 SPS07 (April 4, 2023), April 2023

2.26.3, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

GPL Version 3, commercial licenses available

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

Linux
OS X
Solaris
Windows

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

JDBC
ODBC

gRPC protocol
TypeDB Console (shell)
TypeDB Studio (Visualisation software- previously TypeDB Workbase)

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

All JVM based languages
Groovy
Java
JavaScript (Node.js)
Python
Scala

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

Sharding

yes

Sharding

by using Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

Multi-source replication

by using Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

by using Apache Kafka and Apache Zookeeper

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

substituted by the relationship feature

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

User concepts

Access control

Security Hooks for custom implementations

yes

at REST API level; other APIs in progress

More information provided by the system vendor

Specific characteristics

TypeDB is a polymorphic database with a conceptual data model, a strong subtyping...
» more

Competitive advantages

TypeDB provides a new level of expressivity, extensibility, interoperability, and...
» more

Typical application scenarios

Life sciences : TypeDB makes working with biological data much easier and accelerates...
» more

Licensing and pricing models

Apache f or language drivers, and AGPL and Commercial for the database server. The...
» 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.