DBMS > Hazelcast vs. Percona Server for MySQL vs. Prometheus vs. SQLite

System Properties Comparison Hazelcast vs. Percona Server for MySQL vs. Prometheus vs. SQLite

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

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

Open-source Time Series DBMS and monitoring system

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	2.10
Rank	#119	Overall
	#57	Relational DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

hazelcast.com

www.percona.com/software/mysql-database/percona-server

prometheus.io

www.sqlite.org

Technical documentation

hazelcast.org/imdg/docs

www.percona.com/downloads/Percona-Server-LATEST

prometheus.io/docs

www.sqlite.org/docs.html

Developer

Hazelcast

Percona

Dwayne Richard Hipp

Initial release

2008

2015

2000

Current release

5.3.6, November 2023

8.0.36-28, 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL version 2

Open Source

Apache 2.0

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C and C++

Server operating systems

All OS with a Java VM

Linux

Linux
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Numeric data only

yes

not rigid because of 'dynamic typing' concept.

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

yes

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Multi-source replication
Source-replica replication
XtraDB Cluster

yes

by Federation

none

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

Immediate Consistency

none

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

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Role-based access control

Users with fine-grained authorization concept

no user groups or 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.