DBMS > DuckDB vs. Geode vs. Hazelcast vs. MySQL

System Properties Comparison DuckDB vs. Geode vs. Hazelcast vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, in-process, column-oriented SQL OLAP RDBMS

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A widely adopted in-memory data grid

Widely used open source RDBMS

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

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	4.57
Rank	#74	Overall
	#40	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

duckdb.org/docs

geode.apache.org/docs

hazelcast.org/imdg/docs

dev.mysql.com/doc

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Hazelcast

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2018

2002

2008

1995

Current release

0.10, February 2024

1.1, February 2017

5.3.6, November 2023

8.4.0, April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

Java

C and C++

Server operating systems

server-less

All OS with a Java VM

the JDK (8 or later) is also required

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (OQL)

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

Arrow Database Connectivity (ADBC)
CLI Client
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#

3rd party driver
C++
Crystal

3rd party driver
Go

3rd party driver
Java
Lisp

3rd party driver
Python
R
Ruby

3rd party driver
Rust
Swift
Zig

3rd party driver

.Net
All JVM based languages
C++
Groovy
Java
Scala

.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

Server-side scripts

Stored procedures

user defined functions

yes

Event Listeners, Executor Services

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

Replicated Map

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

ACID

yes, on a single node

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

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

Access rights per client and object definable

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.