DBMS > Hazelcast vs. MaxDB vs. MySQL vs. OrigoDB vs. SWC-DB

System Properties Comparison Hazelcast vs. MaxDB vs. MySQL vs. OrigoDB vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

A robust and reliable RDBMS optimized to run all major SAP solutions

Widely used open source RDBMS

A fully ACID in-memory object graph database

A high performance, scalable Wide Column DBMS

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Document store
Object oriented DBMS

Wide column store

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

Time Series DBMS

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

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

Score	2.15
Rank	#115	Overall
	#55	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	0.01
Rank	#378	Overall
	#13	Wide column stores

Website

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

hazelcast.org/imdg/docs

maxdb.sap.com/documentation

dev.mysql.com/doc

origodb.com/docs

Developer

Hazelcast

SAP, acquired from Software AG (Adabas-D) in 1997

Oracle

since 2010, originally MySQL AB, then Sun

Robert Friberg et al

Alex Kashirin

Initial release

2008

1984

1995

2009

under the name LiveDB

2020

Current release

5.3.6, November 2023

7.9.10.12, February 2024

9.0.0, July 2024

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Limited community edition free

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V3

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

C and C++

C++

Server operating systems

All OS with a Java VM

AIX
HP-UX
Linux
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
WebDAV

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP API
LINQ

Proprietary protocol
Thrift

Supported programming languages

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

.Net
C#
Java
Perl
PHP
Python

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

.Net

C++

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

proprietary syntax

yes

Triggers

yes

Events

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Source-replica replication

Multi-source replication
Source-replica 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 or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

depending on model

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

ACID

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

Write ahead log

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Role based authorization

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.