DBMS > Apache Pinot vs. Microsoft Azure Table Storage vs. PlanetScale vs. Postgres-XL vs. SAP HANA

System Properties Comparison Apache Pinot vs. Microsoft Azure Table Storage vs. PlanetScale vs. Postgres-XL vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

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

A Wide Column Store for rapid development using massive semi-structured datasets

Scalable, distributed, serverless MySQL database platform built on top of Vitess

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

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Wide column store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.38
Rank	#275	Overall
	#126	Relational DBMS

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

pinot.apache.org

azure.microsoft.com/en-us/services/storage/tables

planetscale.com

www.postgres-xl.org

www.sap.com/products/hana.html

Technical documentation

docs.pinot.apache.org

planetscale.com/docs

www.postgres-xl.org/documentation

help.sap.com/hana

Developer

Apache Software Foundation and contributors

Microsoft

PlanetScale

SAP

Initial release

2015

2012

2020

2014

since 2012, originally named StormDB

2010

Current release

1.0.0, September 2023

10 R1, October 2018

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Mozilla public license

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

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

Docker
Linux
macOS

Linux
macOS

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

yes

distributed, parallel query execution

yes

APIs and other access methods

JDBC

RESTful HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

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

JDBC
ODBC

Supported programming languages

Go
Java
Python

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Implicit feature of the cloud service

Sharding

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

optimistic locking

ACID at shard level

ACID

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Access rights based on private key authentication or shared access signatures

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

yes

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.