DBMS > Amazon Redshift vs. Drizzle vs. RDF4J vs. SwayDB vs. XTDB

System Properties Comparison Amazon Redshift vs. Drizzle vs. RDF4J vs. SwayDB vs. XTDB

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

Large scale data warehouse service for use with business intelligence tools

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.

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

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

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

aws.amazon.com/redshift

rdf4j.org

swaydb.simer.au

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.aws.amazon.com/redshift

rdf4j.org/documentation

www.xtdb.com/docs

Developer

Amazon (based on PostgreSQL)

Drizzle project, originally started by Brian Aker

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

Simer Plaha

Juxt Ltd.

Initial release

2012

2008

2004

2018

2019

Current release

7.2.4, September 2012

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

GNU Affero GPL V3.0

Open Source

MIT License

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

Clojure

Server operating systems

hosted

FreeBSD
Linux
OS X

Linux
OS X
Unix
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

RDF Schemas

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

JDBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

Java
PHP
Python

Java
Kotlin
Scala

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

yes, each node contains all data

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

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

Atomic execution of operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.