DBMS > BoltDB vs. Greenplum vs. Hawkular Metrics vs. Microsoft Azure Cosmos DB vs. Prometheus

System Properties Comparison BoltDB vs. Greenplum vs. Hawkular Metrics vs. Microsoft Azure Cosmos DB vs. Prometheus

Editorial information provided by DB-Engines

Name

Description

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

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

Globally distributed, horizontally scalable, multi-model database service

Open-source Time Series DBMS and monitoring system

Primary database model

Key-value store

Relational DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	0.08
Rank	#366	Overall
	#39	Time Series DBMS

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

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Website

github.com/boltdb/bolt

greenplum.org

www.hawkular.org

azure.microsoft.com/services/cosmos-db

prometheus.io

Technical documentation

docs.greenplum.org

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

learn.microsoft.com/azure/cosmos-db

prometheus.io/docs

Developer

Pivotal Software Inc.

Community supported by Red Hat

Microsoft

Initial release

2013

2005

2014

2015

Current release

7.0.0, September 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

Open Source

Apache 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

BSD
Linux
OS X
Solaris
Windows

Linux

Linux
OS X
Windows

hosted

Linux
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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.

yes

since Version 4.2

Import of XML data possible

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC

HTTP REST

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

RESTful HTTP/JSON API

Supported programming languages

C
Java
Perl
Python
R

Go
Java
Python
Ruby

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

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

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes

via Hawkular Alerting

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

selectable replication factor

based on Cassandra

yes

Implicit feature of the cloud service

yes

by Federation

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

Access rights can be defined down to the item level

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.