DBMS > Apache Drill vs. Drizzle vs. Memgraph vs. RocksDB vs. Trafodion

System Properties Comparison Apache Drill vs. Drizzle vs. Memgraph vs. RocksDB vs. Trafodion

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.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Relational DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	3.02
Rank	#98	Overall
	#8	Graph DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

Technical documentation

drill.apache.org/docs

memgraph.com/docs

github.com/facebook/rocksdb/wiki

trafodion.apache.org/documentation.html

Social network pages

Developer

Apache Software Foundation

Drizzle project, originally started by Brian Aker

Memgraph Ltd

Facebook, Inc.

Apache Software Foundation, originally developed by HP

Initial release

2012

2008

2017

2013

2014

Current release

1.20.3, January 2023

7.2.4, September 2012

8.11.4, April 2024

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GNU GPL

Open Source

BSL 1.1; commercial license for enterprise edition available

Open Source

BSD

Open Source

Apache 2.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.

Implementation language

C++

C and C++

C++

C++, Java

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X

Linux

Data scheme

schema-free

yes

schema-free and schema-optional

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

Bolt protocol
Cypher query language

C++ API
Java API

ADO.NET
JDBC
ODBC

Supported programming languages

C++

C
C++
Java
PHP

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

C
C++
Go
Java
Perl
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

dynamic graph partitioning

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication using RAFT

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

yes

Transaction concepts

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

ACID

with snapshot isolation

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

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

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users, roles and permissions

fine grained access rights according to SQL-standard

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.