DBMS > Drizzle vs. EsgynDB vs. Geode vs. HEAVY.AI

System Properties Comparison Drizzle vs. EsgynDB vs. Geode vs. HEAVY.AI

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.

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Website

www.esgyn.cn

geode.apache.org

github.com/heavyai/heavydb
www.heavy.ai

Technical documentation

geode.apache.org/docs

docs.heavy.ai

Developer

Drizzle project, originally started by Brian Aker

Esgyn

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

HEAVY.AI, Inc.

Initial release

2008

2015

2002

2016

Current release

7.2.4, September 2012

1.1, February 2017

5.10, January 2022

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache Version 2; enterprise edition available

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

C++ and CUDA

Server operating systems

FreeBSD
Linux
OS X

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like query language (OQL)

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
Thrift
Vega

Supported programming languages

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

.Net
All JVM based languages
C++
Groovy
Java
Scala

All languages supporting JDBC/ODBC/Thrift
Python

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

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

fine grained access rights according to SQL-standard

Access rights per client and object definable

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.

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

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, O'Reilly Media

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

Big Data Analytics: A Game Changer for Infrastructure
13 July 2023, Spiceworks News and Insights

HEAVY.AI Launches HEAVY 7.0, Introducing Real-Time Machine Learning Capabilities
19 April 2023, Business Wire

Making the most of geospatial intelligence
14 April 2023, InfoWorld

HEAVY.AI Partners with Bain, Maxar, and Nvidia to Provide Digital Twins for Telecom Networks
16 February 2023, Datanami

The insideBIGDATA IMPACT 50 List for Q4 2023
11 October 2023, insideBIGDATA

provided by Google News

Share this page