DBMS > GridGain vs. SAP HANA vs. TempoIQ vs. Yanza

System Properties Comparison GridGain vs. SAP HANA vs. TempoIQ vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

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

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

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Time Series DBMS for IoT Applications

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Time Series 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	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.gridgain.com

www.sap.com/products/hana.html

tempoiq.com (offline)

yanza.com

Technical documentation

www.gridgain.com/docs/index.html

help.sap.com/hana

Developer

GridGain Systems, Inc.

SAP

TempoIQ

Yanza

Initial release

2007

2010

2012

2015

Current release

GridGain 8.5.1

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

free version available

Cloud-based only

Only available as a cloud service

also available as a cloud based service

yes

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

Server operating systems

Linux
OS X
Solaris
Windows

Appliance or cloud-service

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

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

JDBC
ODBC

HTTP API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C#
Java
JavaScript

Node.js
Python
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

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

SQLScript, R

Triggers

yes (cache interceptors and events)

yes

Realtime Alerts

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

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

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

User concepts

Access control

Security Hooks for custom implementations

yes

simple authentication-based access control

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.