DBMS > Drizzle vs. EsgynDB vs. GBase vs. Ignite vs. Tkrzw

System Properties Comparison Drizzle vs. EsgynDB vs. GBase vs. Ignite vs. Tkrzw

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

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Key-value store

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

Technical documentation

apacheignite.readme.io/docs

Developer

Drizzle project, originally started by Brian Aker

Esgyn

General Data Technology Co., Ltd.

Apache Software Foundation

Mikio Hirabayashi

Initial release

2008

2015

2004

2015

2020

Current release

7.2.4, September 2012

GBase 8a, GBase 8s, GBase 8c

Apache Ignite 2.6

0.9.3, August 2020

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2.0

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

C, Java, Python

C++, Java, .Net

C++

Server operating systems

FreeBSD
Linux
OS X

Linux

Linux
OS X
Solaris
Windows

Linux
macOS

Data scheme

yes

schema-free

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

Standard with numerous extensions

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

ADO.NET
C API
JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Supported programming languages

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Java
PHP
Python
Ruby
Scala

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

yes (compute grid and cache interceptors can be used instead)

Triggers

hooks for callbacks inside the server can be used.

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by range, list and hash) and vertical partitioning

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

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

using specific database classes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

yes

Security Hooks for custom implementations

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

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

Apache Ignite: An Overview
6 September 2023, Open Source For You

GridGain Releases Conference Schedule for Virtual Apache Ignite Summit 2023
1 June 2023, Datanami

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

Real-time in-memory OLTP and Analytics with Apache Ignite on AWS | Amazon Web Services
14 May 2016, AWS Blog

provided by Google News

Share this page