DBMS > Amazon Redshift vs. Drizzle vs. EXASOL vs. Memcached vs. RDF4J

System Properties Comparison Amazon Redshift vs. Drizzle vs. EXASOL vs. Memcached vs. RDF4J

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.

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

In-memory key-value store, originally intended for caching

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

Primary database model

Relational DBMS

Key-value store

RDF store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Website

aws.amazon.com/redshift

www.exasol.com

www.memcached.org

rdf4j.org

Technical documentation

docs.aws.amazon.com/redshift

www.exasol.com/resources

github.com/memcached/memcached/wiki

rdf4j.org/documentation

Developer

Amazon (based on PostgreSQL)

Drizzle project, originally started by Brian Aker

Exasol

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

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

Initial release

2012

2008

2000

2003

2004

Current release

7.2.4, September 2012

1.6.27, May 2024

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

Open Source

BSD license

Open Source

Eclipse Distribution License (EDL), v1.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

C++

Java

Server operating systems

hosted

FreeBSD
Linux
OS X

FreeBSD
Linux
OS X
Unix
Windows

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

yes

RDF Schemas

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC

JDBC

.Net
JDBC
ODBC
WebSocket

Proprietary protocol

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

Java
Lua
Python
R

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

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

Repcached, a Memcached patch, provides this functionallity

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

Access rights for users, groups and roles according to SQL-standard

yes

using SASL (Simple Authentication and Security Layer) protocol

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.