DBMS > Apache Pinot vs. Coveo vs. Faircom EDGE vs. SAP HANA

System Properties Comparison Apache Pinot vs. Coveo vs. Faircom EDGE vs. SAP HANA

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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

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

Primary database model

Relational DBMS

Search engine

Key-value store
Relational DBMS

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	0.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

pinot.apache.org

www.coveo.com

www.faircom.com/products/faircom-edge

www.sap.com/products/hana.html

Technical documentation

docs.pinot.apache.org

docs.coveo.com

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

help.sap.com/hana

Developer

Apache Software Foundation and contributors

Coveo

FairCom Corporation

SAP

Initial release

2015

2012

1979

2010

Current release

1.0.0, September 2023

V3, October 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Restricted, free version available

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

ANSI C, C++

Server operating systems

All OS with a Java JDK11 or higher

hosted

Android
Linux

ARM, x86
Raspbian
Windows

Appliance or cloud-service

Data scheme

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

Flexible Schema (defined schema, partial schema, schema free)

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL 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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

ANSI SQL queries

yes

APIs and other access methods

JDBC

RESTful HTTP API

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

JDBC
ODBC

Supported programming languages

Go
Java
Python

C#
Java
JavaScript
Python

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

yes

File partitioning

Customizable business rules for partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency
Tunable Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

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

granular access controls, API key management, content filters

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

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.