DBMS > Graph Engine vs. HEAVY.AI vs. KairosDB vs. Snowflake vs. Warp 10

System Properties Comparison Graph Engine vs. HEAVY.AI vs. KairosDB vs. Snowflake vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Cloud-based data warehousing service for structured and semi-structured data

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Graph DBMS
Key-value store

Secondary database models

Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

www.graphengine.io

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

github.com/kairosdb/kairosdb

www.snowflake.com

www.warp10.io

Technical documentation

www.graphengine.io/docs/manual

docs.heavy.ai

kairosdb.github.io

docs.snowflake.net/manuals/index.html

www.warp10.io/content/02_Getting_started

Developer

Microsoft

HEAVY.AI, Inc.

Snowflake Computing Inc.

SenX

Initial release

2010

2016

2013

2014

2015

Current release

5.10, January 2022

1.2.2, November 2018

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

commercial

Open Source

Apache License 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

.NET and C

C++ and CUDA

Java

Server operating systems

.NET

Linux

Linux
OS X
Windows

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
Thrift
Vega

Graphite protocol
HTTP REST
Telnet API

CLI Client
JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

C#
C++
F#
Visual Basic

All languages supporting JDBC/ODBC/Thrift
Python

Java
JavaScript

Node.js
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

yes

WarpScript

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Round robin

Sharding

based on Cassandra

yes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication factor

based on Cassandra

yes

selectable replication factor

based on HBase

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

based on HBase

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

fine grained access rights according to SQL-standard

simple password-based access control

Users with fine-grained authorization concept, user roles and pluggable authentication

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.