DBMS > HEAVY.AI vs. KairosDB vs. Machbase Neo vs. SAP HANA

System Properties Comparison HEAVY.AI vs. KairosDB vs. Machbase Neo vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Distributed Time Series DBMS based on Cassandra or H2

TimeSeries DBMS for AIoT and BigData

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

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial 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.41
Rank	#153	Overall
	#71	Relational DBMS

Score	0.60
Rank	#238	Overall
	#20	Time Series DBMS

Score	0.07
Rank	#348	Overall
	#34	Time Series DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

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

github.com/kairosdb/kairosdb

machbase.com

www.sap.com/products/hana.html

Technical documentation

Developer

HEAVY.AI, Inc.

Machbase

SAP

Initial release

2016

2013

2010

Current release

5.10, January 2022

1.2.2, November 2018

V8.0, August 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

commercial

free test version 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++ and CUDA

Java

Server operating systems

Linux

Linux
OS X
Windows

Linux
macOS
Windows

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
Thrift
Vega

Graphite protocol
HTTP REST
Telnet API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

Java
JavaScript

Node.js
PHP
Python

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Server-side scripts

Stored procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

based on Cassandra

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication factor

based on Cassandra

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

volatile and lookup table

yes

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based access control

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.