DBMS > 4D vs. Hazelcast vs. LevelDB vs. MySQL vs. SWC-DB

System Properties Comparison 4D vs. Hazelcast vs. LevelDB vs. MySQL vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

A widely adopted in-memory data grid

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Widely used open source RDBMS

A high performance, scalable Wide Column DBMS

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

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	2.37
Rank	#110	Overall
	#54	Relational DBMS

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

Score	2.33
Rank	#111	Overall
	#19	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.01
Rank	#378	Overall
	#13	Wide column stores

Website

www.4d.com

hazelcast.com

github.com/google/leveldb

www.mysql.com

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

Technical documentation

developer.4d.com

hazelcast.org/imdg/docs

github.com/google/leveldb/blob/main/doc/index.md

dev.mysql.com/doc

Developer

4D, Inc

Hazelcast

Google

Oracle

since 2010, originally MySQL AB, then Sun

Alex Kashirin

Initial release

1984

2008

2011

1995

2020

Current release

v20, April 2023

5.3.6, November 2023

1.23, February 2021

9.0.0, July 2024

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD

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

OS X
Windows

All OS with a Java VM

Illumos
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

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

yes

close to SQL 92

SQL-like query language

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary protocol
Thrift

Supported programming languages

4D proprietary IDE
PHP

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

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

C++

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

proprietary syntax

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Replicated Map

none

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

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

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

ACID

not for MyISAM storage engine

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

with automatic compression on writes

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

Users and groups

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.