DBMS > Drizzle vs. HarperDB vs. Microsoft SQL Server vs. RDF4J

System Properties Comparison Drizzle vs. HarperDB vs. Microsoft SQL Server vs. RDF4J

Please select another system to include it in the comparison.

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.

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Microsofts flagship relational DBMS

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

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Website

www.harperdb.io

www.microsoft.com/en-us/sql-server

rdf4j.org

Technical documentation

docs.harperdb.io/docs

learn.microsoft.com/en-US/sql/sql-server

rdf4j.org/documentation

Developer

Drizzle project, originally started by Brian Aker

HarperDB

Microsoft

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

Initial release

2008

2017

1989

2004

Current release

7.2.4, September 2012

3.1, August 2021

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

GNU GPL

commercial

free community edition available

commercial

restricted free version is available

Open Source

Eclipse Distribution License (EDL), v1.0.

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

Node.js

C++

Java

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X

Linux
Windows

Linux
OS X
Unix
Windows

Data scheme

yes

dynamic schema

yes

RDF Schemas

Typing

predefined data types such as float or date

yes

JSON data types

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

SQL-like data manipulation statements

yes

APIs and other access methods

JDBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

C
C++
Java
PHP

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Java
PHP
Python

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

A table resides as a whole on one (or more) nodes in a cluster

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

the nodes on which a table resides can be defined

yes, but depending on the SQL-Server Edition

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

Atomic execution of specific operations

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users and roles

fine grained access rights according to SQL-standard

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.