DBMS > Drizzle vs. Interbase vs. MySQL vs. SiriDB vs. YottaDB

System Properties Comparison Drizzle vs. Interbase vs. MySQL vs. SiriDB vs. YottaDB

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.

Light-weight proven RDBMS

originally from Borland

Widely used open source RDBMS

Open Source Time Series DBMS

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.20
Rank	#317	Overall
	#47	Key-value stores

Website

www.embarcadero.com/products/interbase

www.mysql.com

siridb.com

yottadb.com

Technical documentation

docs.embarcadero.com/products/interbase

dev.mysql.com/doc

docs.siridb.com

yottadb.com/resources/documentation

Developer

Drizzle project, originally started by Brian Aker

Embarcadero

Oracle

since 2010, originally MySQL AB, then Sun

Cesbit

YottaDB, LLC

Initial release

2008

1984

1995

2017

2001

Current release

7.2.4, September 2012

InterBase 2020, December 2019

8.4.0, April 2024

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MIT License

Open Source

AGPL 3.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.

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

Implementation language

C++

C and C++

Server operating systems

FreeBSD
Linux
OS X

Android
iOS
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Docker
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data

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.

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

by using the Octo plugin

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

C
C++
Java
PHP

.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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

yes

proprietary syntax

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Interbase Change Views

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

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

simple rights management via user accounts

Users and groups based on OS-security mechanisms

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.