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

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

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

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	2.52
Rank	#109	Overall
	#9	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

hazelcast.com

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

questdb.io

www.sap.com/products/hana.html

Technical documentation

hazelcast.org/imdg/docs

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

questdb.io/docs

help.sap.com/hana

Developer

Hazelcast

Percona

QuestDB Technology Inc

SAP

Initial release

2008

2015

2014

2010

Current release

5.3.6, November 2023

3.4.10-2.10, November 2017

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL Version 2

Open Source

Apache 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 (Zero-GC), C++, Rust

Server operating systems

All OS with a Java VM

Linux

Linux
macOS
Windows

Appliance or cloud-service

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.

yes

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

SQL with time-series extensions

yes

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

proprietary protocol using JSON

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

JDBC
ODBC

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

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

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

JavaScript

SQLScript, R

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by timestamps)

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Source-replica replication

Source-replica replication with eventual consistency

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

ACID for single-table writes

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

via In-Memory Engine

yes

through memory mapped files

yes

User concepts

Access control

Role-based 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

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

Create an ADS-B flight radar with QuestDB and a Raspberry Pi
8 April 2024

Build a temperature IoT sensor with Raspberry Pi Pico & QuestDB
5 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.