DBMS > Hazelcast vs. OpenQM vs. Oracle vs. PlanetScale

System Properties Comparison Hazelcast vs. OpenQM vs. Oracle vs. PlanetScale

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

QpenQM is a high-performance, self-tuning, multi-value DBMS

Widely used RDBMS

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Primary database model

Key-value store

Multivalue DBMS

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Document store
Spatial DBMS

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

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

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Website

hazelcast.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.oracle.com/database

planetscale.com

Technical documentation

hazelcast.org/imdg/docs

docs.oracle.com/en/database

planetscale.com/docs

Developer

Hazelcast

Rocket Software, originally Martin Phillips

Oracle

PlanetScale

Initial release

2008

1993

1980

2020

Current release

5.3.6, November 2023

3.4-12

23c, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

GPLv2, extended commercial license available

commercial

restricted free version is available

commercial

Cloud-based only

Only available as a cloud service

yes

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

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Docker
Linux
macOS

Data scheme

schema-free

yes

with some exceptions

yes

Schemaless in JSON and XML columns

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

SQL-like query language

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

.Net
Basic
C
Java
Objective C
PHP
Python

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

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

yes

Event Listeners, Executor Services

yes

PL/SQL

also stored procedures in Java possible

yes

proprietary syntax

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

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

isolation level can be parameterized

ACID at shard level

Concurrency

Support for concurrent manipulation of data

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

Role-based access control

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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.