DBMS > HEAVY.AI vs. JanusGraph vs. Kinetica vs. SAP HANA vs. Yaacomo

System Properties Comparison HEAVY.AI vs. JanusGraph vs. Kinetica vs. SAP HANA vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Fully vectorized database across both GPUs and CPUs

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

Secondary database models

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.77
Rank	#141	Overall
	#65	Relational DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

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

janusgraph.org

www.kinetica.com

www.sap.com/products/hana.html

yaacomo.com

Technical documentation

Developer

HEAVY.AI, Inc.

Linux Foundation; originally developed as Titan by Aurelius

Kinetica

SAP

Q2WEB GmbH

Initial release

2016

2017

2012

2010

2009

Current release

5.10, January 2022

0.6.3, February 2023

7.1, August 2021

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

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

C, C++

Server operating systems

Linux

Linux
OS X
Unix
Windows

Linux

Appliance or cloud-service

Android
Linux
Windows

Data scheme

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 DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC
Thrift
Vega

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

Clojure
Java
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

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

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

yes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Source-replica replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

fine grained access rights according to SQL-standard

User authentification and security via Rexster Graph Server

Access rights for users and roles on table level

yes

fine grained access rights according to SQL-standard

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.