DBMS > AgensGraph vs. Hawkular Metrics vs. RavenDB vs. Snowflake

System Properties Comparison AgensGraph vs. Hawkular Metrics vs. RavenDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Primary database model

Graph DBMS
Relational DBMS

Time Series DBMS

Document store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	0.00
Rank	#379	Overall
	#40	Time Series DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

bitnine.net/agensgraph

www.hawkular.org

ravendb.net

www.snowflake.com

Technical documentation

bitnine.net/documentation

www.hawkular.org/hawkular-metrics/docs/user-guide

ravendb.net/docs

docs.snowflake.net/manuals/index.html

Developer

Bitnine Global Inc.

Community supported by Red Hat

Hibernating Rhinos

Snowflake Computing Inc.

Initial release

2016

2014

2010

2014

Current release

2.1, December 2018

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

AGPL version 3, commercial license 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

Java

Server operating systems

Linux
OS X
Windows

Linux
macOS
Raspberry Pi
Windows

hosted

Data scheme

depending on used data model

schema-free

yes

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

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

yes

SQL

Support of SQL

yes

SQL-like query language (RQL)

yes

APIs and other access methods

Cypher Query Language
JDBC

HTTP REST

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

C
Java
JavaScript
Python

Go
Java
Python
Ruby

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

via Hawkular Alerting

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

based on Cassandra

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

based on Cassandra

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

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.

User concepts

Access control

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

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

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.