DBMS > Greenplum vs. Machbase Neo vs. Microsoft Azure Cosmos DB vs. MonetDB

System Properties Comparison Greenplum vs. Machbase Neo vs. Microsoft Azure Cosmos DB vs. MonetDB

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.

TimeSeries DBMS for AIoT and BigData

Globally distributed, horizontally scalable, multi-model database service

A relational database management system that stores data in columns

Primary database model

Relational DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational 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	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

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

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Website

greenplum.org

machbase.com

azure.microsoft.com/services/cosmos-db

www.monetdb.org

Technical documentation

docs.greenplum.org

machbase.com/dbms

learn.microsoft.com/azure/cosmos-db

www.monetdb.org/Documentation

Developer

Pivotal Software Inc.

Machbase

Microsoft

MonetDB BV

Initial release

2005

2013

2014

2004

Current release

7.0.0, September 2023

V8.0, August 2023

Dec2023 (11.49), December 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free test version available

commercial

Open Source

Mozilla Public License 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

Server operating systems

Linux

Linux
macOS
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

since Version 4.2

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

yes

SQL 2003 with some extensions

APIs and other access methods

JDBC
ODBC

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

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

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

Supported programming languages

C
Java
Perl
Python
R

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.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

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

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes

Implicit feature of the cloud service

none

Source-replica replication available in experimental status

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

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

In-memory capabilities

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

yes

volatile and lookup table

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based access control

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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.