DBMS > Drizzle vs. RDF4J vs. Snowflake vs. SwayDB vs. VoltDB

System Properties Comparison Drizzle vs. RDF4J vs. Snowflake vs. SwayDB vs. VoltDB

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.

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Cloud-based data warehousing service for structured and semi-structured data

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

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

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

Technical documentation

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

docs.voltdb.com

Developer

Drizzle project, originally started by Brian Aker

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Snowflake Computing Inc.

Simer Plaha

VoltDB Inc.

Initial release

2008

2004

2014

2018

2010

Current release

7.2.4, September 2012

11.3, April 2022

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Open Source

GNU Affero GPL V3.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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.

Implementation language

C++

Java

Scala

Java, C++

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X
Unix
Windows

hosted

Linux
OS X

for development

Data scheme

yes

RDF Schemas

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

only a subset of SQL 99

APIs and other access methods

JDBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C++
Java
PHP

Java
PHP
Python

JavaScript (Node.js)
Python

Java
Kotlin
Scala

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions

Java

Triggers

hooks for callbacks inside the server can be used.

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Isolation support depends on the API used

ACID

Atomic execution of operations

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

Snapshots and command logging

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

Users with fine-grained authorization concept, user roles and pluggable authentication

Users and roles with access to stored procedures

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.