DBMS > Apache Pinot vs. EsgynDB vs. SAP HANA vs. Transwarp Hippo

System Properties Comparison Apache Pinot vs. EsgynDB vs. SAP HANA vs. Transwarp Hippo

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Cloud-native distributed Vector DBMS that supports storage, retrieval, and management of massive vector-based datasets

Primary database model

Relational DBMS

Vector 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.40
Rank	#270	Overall
	#125	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.00
Rank	#383	Overall
	#13	Vector DBMS

Website

pinot.apache.org

www.esgyn.cn

www.sap.com/products/hana.html

www.transwarp.cn/en/subproduct/hippo

Technical documentation

docs.pinot.apache.org

help.sap.com/hana

Developer

Apache Software Foundation and contributors

Esgyn

SAP

Initial release

2015

2010

2023

Current release

1.0.0, September 2023

2.0 SPS07 (April 4, 2023), April 2023

1.0, May 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Cloud-based only

Only available as a cloud service

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

C++

Server operating systems

All OS with a Java JDK11 or higher

Linux

Appliance or cloud-service

Linux
macOS

Data scheme

yes

Typing

predefined data types such as float or date

yes

Vector, Numeric and String

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

JDBC
ODBC

RESTful HTTP API

Supported programming languages

Go
Java
Python

All languages supporting JDBC/ODBC/ADO.Net

C++
Java
Python

Server-side scripts

Stored procedures

Java Stored Procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

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

User concepts

Access control

fine grained access rights according to SQL-standard

yes

Role based access control and fine grained access rights

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.