DBMS > Hazelcast vs. MySQL vs. ReductStore vs. searchxml

System Properties Comparison Hazelcast vs. MySQL vs. ReductStore vs. searchxml

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

Widely used open source RDBMS

Designed to manage unstructured time-series data efficiently, providing unique features such as storing time-stamped blobs with labels, customizable data retention policies, and a straightforward FIFO quota system.

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Native XML DBMS
Search engine

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

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

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Score	0.00
Rank	#385	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

hazelcast.com

www.mysql.com

github.com/reductstore
www.reduct.store

www.searchxml.net/category/products

Technical documentation

hazelcast.org/imdg/docs

dev.mysql.com/doc

www.reduct.store/docs

www.searchxml.net/support/handouts

Developer

Hazelcast

Oracle

since 2010, originally MySQL AB, then Sun

ReductStore LLC

informationpartners gmbh

Initial release

2008

1995

2023

2015

Current release

5.3.6, November 2023

9.0.0, July 2024

1.9, March 2024

1.0

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Business Source License 1.1

commercial

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

C++, Rust

C++

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS
Windows

Windows

Data scheme

schema-free

yes

schema-free

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

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++
JavaScript (Node.js)
Python
Rust

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

proprietary syntax

yes

on the application server

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Multi-source replication
Source-replica replication

yes

sychronisation to multiple collections

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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

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

ACID

not for MyISAM storage engine

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

Domain, group and role-based access control at the document level and for application services

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.