DBMS > Amazon Redshift vs. Drizzle vs. HarperDB vs. SiteWhere

System Properties Comparison Amazon Redshift vs. Drizzle vs. HarperDB vs. SiteWhere

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

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.

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.

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Document store

Time Series DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

aws.amazon.com/redshift

www.harperdb.io

github.com/sitewhere/sitewhere

Technical documentation

docs.aws.amazon.com/redshift

docs.harperdb.io/docs

sitewhere1.sitewhere.io/index.html

Developer

Amazon (based on PostgreSQL)

Drizzle project, originally started by Brian Aker

HarperDB

SiteWhere

Initial release

2012

2008

2017

2010

Current release

7.2.4, September 2012

3.1, August 2021

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

free community edition available

Open Source

Common Public Attribution License Version 1.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++

Node.js

Java

Server operating systems

hosted

FreeBSD
Linux
OS X

Linux
OS X

Linux
OS X
Windows

Data scheme

yes

dynamic schema

predefined scheme

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

SQL-like data manipulation statements

APIs and other access methods

JDBC
ODBC

JDBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

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

Server-side scripts

Stored procedures

user defined functions

in Python

Custom Functions

since release 3.1

Triggers

hooks for callbacks inside the server can be used.

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

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

the nodes on which a table resides can be defined

selectable replication factor

based on HBase

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

Atomic execution of specific operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

yes

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 and roles

Users with fine-grained authorization concept

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.