DBMS > HugeGraph vs. Microsoft Azure Cosmos DB vs. Netezza vs. Prometheus

System Properties Comparison HugeGraph vs. Microsoft Azure Cosmos DB vs. Netezza vs. Prometheus

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A fast-speed and highly-scalable Graph DBMS

Globally distributed, horizontally scalable, multi-model database service

Data warehouse and analytics appliance part of IBM PureSystems

Open-source Time Series DBMS and monitoring system

Primary database model

Graph DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	0.17
Rank	#335	Overall
	#31	Graph DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	8.59
Rank	#45	Overall
	#29	Relational DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Website

github.com/hugegraph
hugegraph.apache.org

azure.microsoft.com/services/cosmos-db

www.ibm.com/products/netezza

prometheus.io

Technical documentation

hugegraph.apache.org/docs

learn.microsoft.com/azure/cosmos-db

prometheus.io/docs

Developer

Baidu

Microsoft

IBM

Initial release

2018

2014

2000

2015

Current release

0.9

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 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

Java

Server operating systems

Linux
macOS
Unix

hosted

Linux

included in appliance

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

Numeric data only

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.

Import of XML data possible

Secondary indexes

yes

also supports composite index and range index

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

Java API
RESTful HTTP API
TinkerPop Gremlin

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

JDBC
ODBC
OLE DB

RESTful HTTP/JSON API

Supported programming languages

Groovy
Java
Python

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C
C++
Fortran
Java
Lua
Perl
Python
R

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

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

JavaScript

yes

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

yes

depending on used storage backend, e.g. Cassandra and HBase

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

Implicit feature of the cloud service

Source-replica replication

yes

by Federation

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

none

Foreign keys

Referential integrity

yes

edges in graph

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

User concepts

Access control

Users, roles and permissions

Access rights can be defined down to the item level

Users with fine-grained authorization concept

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.