DBMS > Drizzle vs. Geode vs. Infobright vs. MaxDB vs. SAP HANA

System Properties Comparison Drizzle vs. Geode vs. Infobright vs. MaxDB vs. SAP HANA

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.

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

A robust and reliable RDBMS optimized to run all major SAP solutions

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

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

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

geode.apache.org

ignitetech.com/softwarelibrary/infobrightdb

maxdb.sap.com

www.sap.com/products/hana.html

Technical documentation

geode.apache.org/docs

maxdb.sap.com/documentation

help.sap.com/hana

Developer

Drizzle project, originally started by Brian Aker

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

Ignite Technologies Inc.; formerly InfoBright Inc.

SAP, acquired from Software AG (Adabas-D) in 1997

SAP

Initial release

2008

2002

2005

1984

2010

Current release

7.2.4, September 2012

1.1, February 2017

7.9.10.12, February 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

Limited community edition free

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

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

the JDK (8 or later) is also required

Linux
Windows

AIX
HP-UX
Linux
Solaris
Windows

Appliance or cloud-service

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (OQL)

yes

APIs and other access methods

JDBC

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
WebDAV

JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

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

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C#
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

SQLScript, R

Triggers

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

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 per client and object definable

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

yes

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.