DBMS > Drizzle vs. Hazelcast vs. Hyprcubd vs. Ingres vs. RocksDB

System Properties Comparison Drizzle vs. Hazelcast vs. Hyprcubd vs. Ingres vs. RocksDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A widely adopted in-memory data grid

Serverless Time Series DBMS

Well established RDBMS

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

hazelcast.com

hyprcubd.com (offline)

www.actian.com/databases/ingres

rocksdb.org

Technical documentation

hazelcast.org/imdg/docs

docs.actian.com/ingres

github.com/facebook/rocksdb/wiki

Developer

Drizzle project, originally started by Brian Aker

Hazelcast

Hyprcubd, Inc.

Actian Corporation

Facebook, Inc.

Initial release

2008

1974

originally developed at University Berkely in early 1970s

2013

Current release

7.2.4, September 2012

5.3.6, November 2023

11.2, May 2022

9.2.1, May 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

BSD

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

C++

Java

C++

Server operating systems

FreeBSD
Linux
OS X

All OS with a Java VM

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

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

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

yes

APIs and other access methods

JDBC

JCache
JPA
Memcached protocol
RESTful HTTP API

gRPC (https)

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

C++ API
Java API

Supported programming languages

C
C++
Java
PHP

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Replicated Map

Ingres Replicator

yes

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Role-based access control

token access

fine grained access rights according to SQL-standard

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.