DBMS > Apache Pinot vs. Elasticsearch vs. SAP HANA vs. Sphinx vs. Tarantool

System Properties Comparison Apache Pinot vs. Elasticsearch vs. SAP HANA vs. Sphinx vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

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

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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

Open source search engine for searching in data from different sources, e.g. relational databases

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.38
Rank	#275	Overall
	#126	Relational DBMS

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

pinot.apache.org

www.elastic.co/elasticsearch

www.sap.com/products/hana.html

sphinxsearch.com

www.tarantool.io

Technical documentation

docs.pinot.apache.org

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

help.sap.com/hana

sphinxsearch.com/docs

www.tarantool.io/en/doc

Developer

Apache Software Foundation and contributors

Elastic

SAP

Sphinx Technologies Inc.

Initial release

2015

2010

2001

2008

Current release

1.0.0, September 2023

8.6, January 2023

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Elastic License

commercial

Open Source

GPL version 2, commercial licence available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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++

C and C++

Server operating systems

All OS with a Java JDK11 or higher

All OS with a Java VM

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

BSD
Linux
macOS

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

All search fields are automatically indexed

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-like query language (SphinxQL)

Full-featured ANSI SQL support

APIs and other access methods

JDBC

Java API
RESTful HTTP/JSON API

JDBC
ODBC

Proprietary protocol

Open binary protocol

Supported programming languages

Go
Java
Python

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

SQLScript, R

Lua, C and SQL stored procedures

Triggers

yes

by using the 'percolation' feature

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

yes, write ahead logging

In-memory capabilities

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

Memcached and Redis integration

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

yes

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.