DBMS > AlaSQL vs. Amazon Redshift vs. Apache IoTDB vs. Drizzle

System Properties Comparison AlaSQL vs. Amazon Redshift vs. Apache IoTDB vs. Drizzle

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

JavaScript DBMS library

Large scale data warehouse service for use with business intelligence tools

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Primary database model

Document store
Relational DBMS

Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Website

alasql.org

aws.amazon.com/redshift

iotdb.apache.org

Technical documentation

github.com/AlaSQL/alasql

docs.aws.amazon.com/redshift

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

Developer

Andrey Gershun & Mathias R. Wulff

Amazon (based on PostgreSQL)

Apache Software Foundation

Drizzle project, originally started by Brian Aker

Initial release

2014

2012

2018

2008

Current release

1.1.0, April 2023

7.2.4, September 2012

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

Apache Version 2.0

Open Source

GNU GPL

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

JavaScript

Java

C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

hosted

All OS with a Java VM (>= 1.8)

FreeBSD
Linux
OS X

Data scheme

schema-free

yes

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

Close to SQL99, but no user access control, stored procedures and host language bindings.

yes

does not fully support an SQL-standard

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JavaScript API

JDBC
ODBC

JDBC
Native API

JDBC

Supported programming languages

JavaScript

All languages supporting JDBC/ODBC

C
C#
C++
Go
Java
Python
Scala

C
C++
Java
PHP

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Strong Consistency with Raft

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

yes

only for local storage and DOM-storage

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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

yes

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.