DBMS > Drizzle vs. Hazelcast vs. SQLite vs. UniData,UniVerse

System Properties Comparison Drizzle vs. Hazelcast vs. SQLite vs. UniData,UniVerse

Please select another system to include it in the comparison.

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.

Description

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

A widely adopted in-memory data grid

Widely used embeddable, in-process RDBMS

MultiValue database and application server with SQL mapping layer and meta database capabilities

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	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	2.85
Rank	#98	Overall
	#1	Multivalue DBMS

Website

hazelcast.com

www.sqlite.org

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

Technical documentation

hazelcast.org/imdg/docs

www.sqlite.org/docs.html

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

Drizzle project, originally started by Brian Aker

Hazelcast

Dwayne Richard Hipp

Rocket Software

Initial release

2008

2000

1985

Current release

7.2.4, September 2012

5.3.6, November 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available

Open Source

Public Domain

commercial

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

C++

Java

Server operating systems

FreeBSD
Linux
OS X

All OS with a Java VM

server-less

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

optional

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

yes

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

C
C++
Java
PHP

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Events

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Replicated Map

none

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

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

configurable

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Access rights according to SQL-standard and operating system based

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.