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

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

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

Primary database model

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

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

Website

Technical documentation

docs.datomic.com

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

Developer

Cognitect

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

Initial release

2012

2008

2004

2014

2018

Current release

1.0.6735, June 2023

7.2.4, September 2012

License

Commercial or Open Source

commercial

limited edition free

Open Source

GNU GPL

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Open Source

GNU Affero GPL V3.0

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

Java, Clojure

C++

Java

Scala

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X

Linux
OS X
Unix
Windows

hosted

Data scheme

yes

RDF Schemas

yes

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

schema-free

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

APIs and other access methods

RESTful HTTP API

JDBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

Supported programming languages

Clojure
Java

C
C++
Java
PHP

Java
PHP
Python

JavaScript (Node.js)
Python

Java
Kotlin
Scala

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

user defined functions

Triggers

By using transaction functions

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

none

But extensive use of caching in the application peers

Sharding

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication
Source-replica replication

none

yes

none

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

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

in-memory storage is supported as well

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users with fine-grained authorization concept, user roles and pluggable 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.