DBMS > GridGain vs. KairosDB vs. Kinetica vs. SAP HANA

System Properties Comparison GridGain vs. KairosDB vs. Kinetica vs. SAP HANA

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

Distributed Time Series DBMS based on Cassandra or H2

Fully vectorized database across both GPUs and CPUs

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

Primary database model

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

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.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	0.60
Rank	#238	Overall
	#20	Time Series DBMS

Score	0.42
Rank	#261	Overall
	#120	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

www.gridgain.com

github.com/kairosdb/kairosdb

www.kinetica.com

www.sap.com/products/hana.html

Technical documentation

www.gridgain.com/docs/index.html

kairosdb.github.io

docs.kinetica.com

help.sap.com/hana

Developer

GridGain Systems, Inc.

Kinetica

SAP

Initial release

2007

2013

2012

2010

Current release

GridGain 8.5.1

1.2.2, November 2018

7.1, August 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial, open source

Open Source

Apache 2.0

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, Python, REST, SQL

Java

C, C++

Server operating systems

Linux
OS X
Solaris
Windows
z/OS

Linux
OS X
Windows

Linux

Appliance or cloud-service

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

SQL

Support of SQL

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

SQL-like DML and DDL statements

yes

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Graphite protocol
HTTP REST
Telnet API

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Java
JavaScript

Node.js
PHP
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

user defined functions

SQLScript, R

Triggers

yes (cache interceptors and events)

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

based on Cassandra

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

selectable replication factor

based on Cassandra

Source-replica replication

yes

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

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

Role-based access control
Security Hooks for custom implementations

simple password-based access control

Access rights for users and roles on table level

yes

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.