DBMS > Hazelcast vs. Kinetica vs. Prometheus vs. Snowflake vs. TigerGraph

System Properties Comparison Hazelcast vs. Kinetica vs. Prometheus vs. Snowflake vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

Fully vectorized database across both GPUs and CPUs

Open-source Time Series DBMS and monitoring system

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

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS
Time Series DBMS

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

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

Technical documentation

hazelcast.org/imdg/docs

docs.kinetica.com

prometheus.io/docs

docs.snowflake.net/manuals/index.html

docs.tigergraph.com

Developer

Hazelcast

Kinetica

Snowflake Computing Inc.

Initial release

2008

2012

2015

2014

2017

Current release

5.3.6, November 2023

7.1, August 2021

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Apache 2.0

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

Java

C, C++

C++

Server operating systems

All OS with a Java VM

Linux

Linux
Windows

hosted

Linux

Data scheme

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

Import of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

SQL-like DML and DDL statements

yes

SQL-like query language (GSQL)

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

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

C++
Java
JavaScript (Node.js)
Python

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

user defined functions

yes

Triggers

yes

Events

yes

triggers when inserted values for one or more columns fall within a specified range

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Source-replica replication

yes

by Federation

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 or Eventual Consistency depending on configuration

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

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

User concepts

Access control

Role-based access control

Access rights for users and roles on table level

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

Role-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.