DBMS > Apache Pinot vs. Ignite vs. Microsoft Azure Table Storage vs. SAP HANA vs. Tibero

System Properties Comparison Apache Pinot vs. Ignite vs. Microsoft Azure Table Storage vs. SAP HANA vs. Tibero

Editorial information provided by DB-Engines

Name

Description

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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

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

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Wide column store

Relational DBMS

Secondary database models

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	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Website

pinot.apache.org

ignite.apache.org

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

www.sap.com/products/hana.html

us.tmaxsoft.com/products/tibero

Technical documentation

docs.pinot.apache.org

apacheignite.readme.io/docs

help.sap.com/hana

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Apache Software Foundation and contributors

Apache Software Foundation

Microsoft

SAP

TmaxSoft

Initial release

2015

2012

2010

2003

Current release

1.0.0, September 2023

Apache Ignite 2.6

2.0 SPS07 (April 4, 2023), April 2023

6, April 2015

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

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

C++, Java, .Net

C and Assembler

Server operating systems

All OS with a Java JDK11 or higher

Linux
OS X
Solaris
Windows

hosted

Appliance or cloud-service

AIX
HP-UX
Linux
Solaris
Windows

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

JDBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

RESTful HTTP API

JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

Go
Java
Python

C#
C++
Java
PHP
Python
Ruby
Scala

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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

SQLScript, R

Persistent Stored Procedure (PSM)

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Implicit feature of the cloud service

yes

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes

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

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

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

planned for next version

User concepts

Access control

Security Hooks for custom implementations

Access rights based on private key authentication or shared access signatures

yes

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.