DBMS > Apache Pinot vs. Microsoft Azure Cosmos DB vs. Netezza vs. Postgres-XL

System Properties Comparison Apache Pinot vs. Microsoft Azure Cosmos DB vs. Netezza vs. Postgres-XL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Realtime distributed OLAP datastore, designed to answer OLAP queries with low latency

Globally distributed, horizontally scalable, multi-model database service

Data warehouse and analytics appliance part of IBM PureSystems

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	0.38
Rank	#275	Overall
	#126	Relational 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	0.53
Rank	#254	Overall
	#117	Relational DBMS

Website

pinot.apache.org

azure.microsoft.com/services/cosmos-db

www.ibm.com/products/netezza

www.postgres-xl.org

Technical documentation

docs.pinot.apache.org

learn.microsoft.com/azure/cosmos-db

www.postgres-xl.org/documentation

Developer

Apache Software Foundation and contributors

Microsoft

IBM

Initial release

2015

2014

2000

2014

since 2012, originally named StormDB

Current release

1.0.0, September 2023

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Mozilla public license

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

All OS with a Java JDK11 or higher

hosted

Linux

included in appliance

Linux
macOS

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

XML type, but no XML query functionality

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

distributed, parallel query execution

APIs and other access methods

JDBC

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

JDBC
ODBC
OLE DB

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Go
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
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

JavaScript

yes

user defined functions

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Implicit feature of the cloud service

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

MVCC

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

Access rights can be defined down to the item level

Users with fine-grained authorization concept

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.