DBMS > Drizzle vs. Memgraph vs. MySQL vs. Quasardb vs. Tarantool

System Properties Comparison Drizzle vs. Memgraph vs. MySQL vs. Quasardb vs. Tarantool

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.

An open source graph database built for real-time streaming and compatible with Neo4j

Widely used open source RDBMS

Distributed, high-performance timeseries database

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	3.19
Rank	#94	Overall
	#8	Graph DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

Technical documentation

memgraph.com/docs

dev.mysql.com/doc

doc.quasar.ai/master

www.tarantool.io/en/doc

Social network pages

Developer

Drizzle project, originally started by Brian Aker

Memgraph Ltd

Oracle

since 2010, originally MySQL AB, then Sun

quasardb

Initial release

2008

2017

1995

2009

2008

Current release

7.2.4, September 2012

8.4.0, April 2024

3.14.1, January 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

BSL 1.1; commercial license for enterprise edition available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C++

C and C++

Server operating systems

FreeBSD
Linux
OS X

Linux

FreeBSD
Linux
OS X
Solaris
Windows

BSD
Linux
OS X
Windows

BSD
Linux
macOS

Data scheme

yes

schema-free and schema-optional

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

integer and binary

string, double, decimal, uuid, integer, blob, boolean, datetime

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

with tags

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

SQL-like query language

Full-featured ANSI SQL support

APIs and other access methods

JDBC

Bolt protocol
Cypher query language

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

Open binary protocol

Supported programming languages

C
C++
Java
PHP

.Net
C
C++
Elixir
Go
Haskell
Java
JavaScript
PHP
Python
Ruby
Scala

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

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

proprietary syntax

Lua, C and SQL stored procedures

Triggers

hooks for callbacks inside the server can be used.

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

dynamic graph partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

consistent hashing

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication using RAFT

Multi-source replication
Source-replica replication

Source-replica replication with selectable replication factor

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

relationships in graphs

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

with snapshot isolation

ACID

not for MyISAM storage engine

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

with periodic snapshot and write-ahead logging (WAL) of changes

yes

by using LevelDB

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users, roles and permissions

Users with fine-grained authorization concept

no user groups or roles

Cryptographically strong user authentication and audit trail

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

More information provided by the system vendor

Specific characteristics

Memgraph directly connects to your streaming infrastructure so you and your team...
» more

Competitive advantages

Business Source License ensures a future for the Memgraph community MAGE algorithm...
» more

Typical application scenarios

Graph algorithms in bioinformatics Social network analysis Cryptocurrency network...
» more

Licensing and pricing models

You can check out our pricing model and licenses on the company website .
» more

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.