DBMS > Drizzle vs. EXASOL vs. Hazelcast vs. LeanXcale vs. Snowflake

System Properties Comparison Drizzle vs. EXASOL vs. Hazelcast vs. LeanXcale vs. Snowflake

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.

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

A widely adopted in-memory data grid

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

Key-value store

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	1.66
Rank	#138	Overall
	#64	Relational DBMS

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

Score	0.28
Rank	#286	Overall
	#41	Key-value stores
	#130	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

Technical documentation

www.exasol.com/resources

hazelcast.org/imdg/docs

docs.snowflake.net/manuals/index.html

Developer

Drizzle project, originally started by Brian Aker

Exasol

Hazelcast

LeanXcale

Snowflake Computing Inc.

Initial release

2008

2000

2008

2015

2014

Current release

7.2.4, September 2012

5.3.6, November 2023

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

Apache Version 2; commercial licenses 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

C++

Java

Server operating systems

FreeBSD
Linux
OS X

All OS with a Java VM

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

with proprietary extensions

yes

SQL-like query language

yes

through Apache Derby

yes

APIs and other access methods

JDBC

.Net
JDBC
ODBC
WebSocket

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

CLI Client
JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

Java
Lua
Python
R

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

C
Java
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

Event Listeners, Executor Services

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Replicated Map

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

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

Transaction concepts

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

ACID

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

ACID

Concurrency

Support for concurrent manipulation of data

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

Access rights for users, groups and roles according to SQL-standard

Role-based access control

Users with fine-grained authorization concept, user roles and pluggable authentication

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.