DBMS > Drizzle vs. EsgynDB vs. Hazelcast vs. SwayDB vs. XTDB

System Properties Comparison Drizzle vs. EsgynDB vs. Hazelcast vs. SwayDB vs. XTDB

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.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

A widely adopted in-memory data grid

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Key-value store

Document store

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

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

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

www.esgyn.cn

hazelcast.com

swaydb.simer.au

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

hazelcast.org/imdg/docs

www.xtdb.com/docs

Developer

Drizzle project, originally started by Brian Aker

Esgyn

Hazelcast

Simer Plaha

Juxt Ltd.

Initial release

2008

2015

2008

2018

2019

Current release

7.2.4, September 2012

5.3.6, November 2023

1.19, September 2021

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

GNU Affero GPL V3.0

Open Source

MIT License

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++

C++, Java

Java

Scala

Clojure

Server operating systems

FreeBSD
Linux
OS X

Linux

All OS with a Java VM

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

yes

SQL-like query language

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

HTTP REST
JDBC

Supported programming languages

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

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

Java
Kotlin
Scala

Clojure
Java

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Event Listeners, Executor Services

Triggers

hooks for callbacks inside the server can be used.

yes

Events

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

Multi-source replication between multi datacenters

yes

Replicated Map

none

yes, each node contains all data

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

Transaction concepts

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

ACID

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

Atomic execution of operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

fine grained access rights according to SQL-standard

Role-based access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Hazelcast Weaves Wider Logic Threads Through The Data Fabric
7 March 2024, Forbes

Hazelcast appoints Anthony Griffin as Chief Architect -
11 June 2024, Enterprise Times

Hazelcast 5.4 real time data processing platform boosts AI and consistency
17 April 2024, VentureBeat

Hazelcast Achieves Record Year with Leading Brands Choosing Its Platform for Application Modernization, AI Initiatives
22 February 2024, Datanami

Hazelcast Versus Redis: A Practical Comparison
4 January 2024, Database Trends and Applications

provided by Google News

Share this page