DBMS > Dgraph vs. Drizzle vs. KeyDB vs. Oracle Coherence vs. RocksDB

System Properties Comparison Dgraph vs. Drizzle vs. KeyDB vs. Oracle Coherence vs. RocksDB

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

Distributed and scalable native Graph DBMS

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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Oracles in-memory data grid solution

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

Primary database model

Graph DBMS

Relational DBMS

Key-value store

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	1.92
Rank	#130	Overall
	#22	Key-value stores

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

Website

dgraph.io

github.com/Snapchat/KeyDB
keydb.dev

www.oracle.com/java/coherence

rocksdb.org

Technical documentation

dgraph.io/docs

docs.keydb.dev

docs.oracle.com/en/middleware/standalone/coherence

github.com/facebook/rocksdb/wiki

Developer

Dgraph Labs, Inc.

Drizzle project, originally started by Brian Aker

EQ Alpha Technology Ltd.

Oracle

Facebook, Inc.

Initial release

2016

2008

2019

2007

2013

Current release

7.2.4, September 2012

14.1, August 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GNU GPL

Open Source

BSD-3

commercial

Open Source

BSD

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

Java

C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X

Linux

All OS with a Java VM

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JDBC

Proprietary protocol

RESP - REdis Serialization Protoco

JCache
JPA
RESTful HTTP API

C++ API
Java API

Supported programming languages

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

C
C++
Java
PHP

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

.Net
C++
Java

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Lua

Triggers

hooks for callbacks inside the server can be used.

yes

Live Events

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication
Source-replica replication

yes, with selectable consistency level

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

configurable

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

optionally

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

Planned for future releases

Pluggable authentication mechanisms

e.g. LDAP, HTTP

simple password-based access control and ACL

authentification to access the cache via certificates or http basic authentication

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.