DBMS > Drizzle vs. DuckDB vs. GeoSpock vs. MySQL

System Properties Comparison Drizzle vs. DuckDB vs. GeoSpock vs. MySQL

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.

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

An embeddable, in-process, column-oriented SQL OLAP RDBMS

Spatial and temporal data processing engine for extreme data scale

Widely used open source RDBMS

Primary database model

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	4.57
Rank	#74	Overall
	#40	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

duckdb.org

geospock.com

www.mysql.com

Technical documentation

duckdb.org/docs

dev.mysql.com/doc

Developer

Drizzle project, originally started by Brian Aker

GeoSpock

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2008

2018

1995

Current release

7.2.4, September 2012

0.10, February 2024

2.0, September 2019

8.4.0, April 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

MIT License

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

yes

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++

Java, Javascript

C and C++

Server operating systems

FreeBSD
Linux
OS X

server-less

hosted

FreeBSD
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

temporal, categorical

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

ANSI SQL for query only (using Presto)

yes

with proprietary extensions

APIs and other access methods

JDBC

Arrow Database Connectivity (ADBC)
CLI Client
JDBC
ODBC

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C++
Java
PHP

C
C#

3rd party driver
C++
Crystal

3rd party driver
Go

3rd party driver
Java
Lisp

3rd party driver
Python
R
Ruby

3rd party driver
Rust
Swift
Zig

3rd party driver

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

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

Automatic sharding

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

none

Multi-source replication
Source-replica replication

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

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users can be defined per table

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.