DBMS > Drizzle vs. MySQL vs. Realm vs. SAP SQL Anywhere

System Properties Comparison Drizzle vs. MySQL vs. Realm vs. SAP SQL Anywhere

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.

Widely used open source RDBMS

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

www.mysql.com

realm.io

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

dev.mysql.com/doc

realm.io/docs

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Drizzle project, originally started by Brian Aker

Oracle

since 2010, originally MySQL AB, then Sun

Realm, acquired by MongoDB in May 2019

SAP

formerly Sybase

Initial release

2008

1995

2014

1992

Current release

7.2.4, September 2012

8.4.0, April 2024

17, July 2015

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

commercial

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

FreeBSD
Linux
OS X
Solaris
Windows

Android
Backend: server-less
iOS
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

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

.Net
Java

with Android only
Objective-C
React Native
Swift

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax

runs within the applications so server-side scripts are unnecessary

yes, in C/C++, Java, .Net or Perl

Triggers

hooks for callbacks inside the server can be used.

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Source-replica replication

Database mirroring

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

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

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

In-Memory realm

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users with fine-grained authorization concept

no user groups or roles

yes

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.