DBMS > Graph Engine vs. Hazelcast vs. HEAVY.AI vs. Snowflake vs. TempoIQ

System Properties Comparison Graph Engine vs. Hazelcast vs. HEAVY.AI vs. Snowflake vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

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

A widely adopted in-memory data grid

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

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

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Graph DBMS
Key-value store

Key-value store

Relational DBMS

Time Series DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.graphengine.io

hazelcast.com

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

www.snowflake.com

tempoiq.com (offline)

Technical documentation

www.graphengine.io/docs/manual

hazelcast.org/imdg/docs

docs.heavy.ai

docs.snowflake.net/manuals/index.html

Developer

Microsoft

Hazelcast

HEAVY.AI, Inc.

Snowflake Computing Inc.

TempoIQ

Initial release

2010

2008

2016

2014

2012

Current release

5.3.6, November 2023

5.10, January 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache Version 2; enterprise edition available

commercial

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

Java

C++ and CUDA

Server operating systems

.NET

All OS with a Java VM

Linux

hosted

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC
Thrift
Vega

CLI Client
JDBC
ODBC

HTTP API

Supported programming languages

C#
C++
F#
Visual Basic

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript (Node.js)
Python

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

user defined functions

Triggers

yes

Events

similar concept for controling cloud resources

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Round robin

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

one or two-phase-commit; repeatable reads; read commited

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

Role-based access control

fine grained access rights according to SQL-standard

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

simple authentication-based access control

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.