DBMS > Greenplum vs. Microsoft Azure Cosmos DB vs. MonetDB vs. Quasardb

System Properties Comparison Greenplum vs. Microsoft Azure Cosmos DB vs. MonetDB vs. Quasardb

Please select another system to include it in the comparison.

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.

Globally distributed, horizontally scalable, multi-model database service

A relational database management system that stores data in columns

Distributed, high-performance timeseries database

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

Document store
Spatial DBMS

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

Score	9.23
Rank	#47	Overall
	#30	Relational DBMS

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

Score	1.72
Rank	#148	Overall
	#68	Relational DBMS

Score	0.19
Rank	#327	Overall
	#30	Time Series DBMS

Website

greenplum.org

azure.microsoft.com/services/cosmos-db

www.monetdb.org

quasar.ai

Technical documentation

docs.greenplum.org

learn.microsoft.com/azure/cosmos-db

www.monetdb.org/Documentation

doc.quasar.ai/master

Developer

Pivotal Software Inc.

Microsoft

MonetDB BV

quasardb

Initial release

2005

2014

2004

2009

Current release

7.0.0, September 2023

Dec2023 (11.49), December 2023

3.14.1, January 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Mozilla Public License 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

C++

Server operating systems

Linux

hosted

FreeBSD
Linux
OS X
Solaris
Windows

BSD
Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

integer and binary

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

Secondary indexes

yes

All properties auto-indexed by default

yes

with tags

SQL

Support of SQL

yes

SQL-like query language

yes

SQL 2003 with some extensions

SQL-like query language

APIs and other access methods

JDBC
ODBC

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

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

HTTP API

Supported programming languages

C
Java
Perl
Python
R

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

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

yes

JavaScript

yes, in SQL, C, R

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding via remote tables

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Implicit feature of the cloud service

none

Source-replica replication available in experimental status

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

by using LevelDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

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.