DBMS > DataFS vs. Drizzle vs. Ignite vs. Interbase vs. MySQL

System Properties Comparison DataFS vs. Drizzle vs. Ignite vs. Interbase vs. MySQL

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

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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.

Light-weight proven RDBMS

originally from Borland

Widely used open source RDBMS

Primary database model

Object oriented DBMS

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Graph DBMS

Document store
Spatial DBMS

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

Score	0.06
Rank	#354	Overall
	#15	Object oriented DBMS

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

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

newdatabase.com

ignite.apache.org

www.embarcadero.com/products/interbase

www.mysql.com

Technical documentation

dev.mobiland.com/Overview.xsp

apacheignite.readme.io/docs

docs.embarcadero.com/products/interbase

dev.mysql.com/doc

Developer

Mobiland AG

Drizzle project, originally started by Brian Aker

Apache Software Foundation

Embarcadero

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2018

2008

2015

1984

1995

Current release

1.1.263, October 2022

7.2.4, September 2012

Apache Ignite 2.6

InterBase 2020, December 2019

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

Apache 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C++, Java, .Net

C and C++

Server operating systems

Windows

FreeBSD
Linux
OS X

Linux
OS X
Solaris
Windows

Android
iOS
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

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.

yes

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

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

yes

with proprietary extensions

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

JDBC

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

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C#
C++
VB.Net

C
C++
Java
PHP

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

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

yes

Interbase procedure and trigger language

yes

proprietary syntax

Triggers

no, except callback-events from server when changes happened

hooks for callbacks inside the server can be used.

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Proprietary Sharding system

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes (replicated cache)

Interbase Change Views

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

table locks or row locks depending on storage engine

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

Windows-Profile

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.