DBMS > Percona Server for MongoDB vs. QuestDB vs. SAP HANA vs. Sphinx

System Properties Comparison Percona Server for MongoDB vs. QuestDB vs. SAP HANA vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

A high performance open source SQL database for time series data

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

Primary database model

Secondary database models

Relational 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.60
Rank	#246	Overall
	#39	Document stores

Score	2.70
Rank	#105	Overall
	#8	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

www.percona.com/mongodb/software/percona-server-for-mongodb

questdb.io

www.sap.com/products/hana.html

sphinxsearch.com

Technical documentation

docs.percona.com/percona-distribution-for-mongodb

questdb.io/docs

help.sap.com/hana

sphinxsearch.com/docs

Developer

Percona

QuestDB Technology Inc

SAP

Sphinx Technologies Inc.

Initial release

2015

2014

2010

2001

Current release

3.4.10-2.10, November 2017

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

License

Commercial or Open Source

Open Source

GPL Version 2

Open Source

Apache 2.0

commercial

Open Source

GPL version 2, commercial licence available

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

C++

Java (Zero-GC), C++, Rust

C++

Server operating systems

Linux

Linux
macOS
Windows

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free via InfluxDB Line Protocol

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.

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

SQL with time-series extensions

yes

SQL-like query language (SphinxQL)

APIs and other access methods

proprietary protocol using JSON

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

JDBC
ODBC

Proprietary protocol

Supported programming languages

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

JavaScript

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by timestamps)

yes

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Source-replica replication with eventual consistency

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID for single-table writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

In-memory capabilities

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

yes

via In-Memory Engine

yes

through memory mapped files

yes

User concepts

Access control

Access rights for users and roles

yes

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

Fluid real-time dashboards with Grafana and QuestDB
11 June 2024

QuestDB 8.0: Major Release
23 May 2024

QuestDB and Raspberry Pi 5 benchmark, a pocket-sized powerhouse
8 May 2024

Build your own resource monitor with QuestDB and Grafana
6 May 2024

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

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.