DBMS > GridDB vs. HEAVY.AI vs. Kinetica vs. SAP HANA

System Properties Comparison GridDB vs. HEAVY.AI vs. Kinetica 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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Fully vectorized database across both GPUs and CPUs

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

Primary database model

Time Series DBMS

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

Spatial DBMS

Spatial DBMS
Time Series 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	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

griddb.net

github.com/heavyai/heavydb
www.heavy.ai

www.kinetica.com

www.sap.com/products/hana.html

Technical documentation

Developer

Toshiba Corporation

HEAVY.AI, Inc.

Kinetica

SAP

Initial release

2013

2016

2012

2010

Current release

5.1, August 2022

5.10, January 2022

7.1, August 2021

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 Version 2; enterprise edition available

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++

C++ and CUDA

C, C++

Server operating systems

Linux

Appliance or cloud-service

Data scheme

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

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

JDBC
ODBC
Thrift
Vega

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

Supported programming languages

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

All languages supporting JDBC/ODBC/Thrift
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

GPU vRAM or System RAM

yes

User concepts

Access control

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

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.