DBMS > AlaSQL vs. Apache Drill vs. DolphinDB vs. Drizzle

System Properties Comparison AlaSQL vs. Apache Drill vs. DolphinDB 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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

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

Primary database model

Document store
Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.49
Rank	#259	Overall
	#40	Document stores
	#120	Relational DBMS

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	4.23
Rank	#82	Overall
	#6	Time Series DBMS

Website

alasql.org

drill.apache.org

www.dolphindb.com

Technical documentation

github.com/AlaSQL/alasql

drill.apache.org/docs

docs.dolphindb.cn/en/help200/index.html

Developer

Andrey Gershun & Mathias R. Wulff

Apache Software Foundation

DolphinDB, Inc

Drizzle project, originally started by Brian Aker

Initial release

2014

2012

2018

2008

Current release

1.20.3, January 2023

v2.00.4, January 2022

7.2.4, September 2012

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2

commercial

free community version available

Open Source

GNU GPL

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

JavaScript

C++

Server operating systems

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

Linux
OS X
Windows

Linux
Windows

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

yes

SQL

Support of SQL

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

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JavaScript API

JDBC
ODBC
RESTful HTTP API

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

JDBC

Supported programming languages

JavaScript

C++

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

C
C++
Java
PHP

Server-side scripts

Stored procedures

user defined functions

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

Depending on the underlying data source

yes

In-memory capabilities

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

yes

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Administrators, Users, Groups

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Create a Marvel Database with SQL and Javascript, the easy way
2 July 2019, Towards Data Science

HarperDB - How and Why We Built It From The Ground Up on NodeJS
28 February 2021, hackernoon.com

Multi faceted data exploration in the browser using Leaflet and amCharts
3 May 2020, Towards Data Science

provided by Google News

Analyse Kafka messages with SQL queries using Apache Drill
23 September 2019, Towards Data Science

Apache Drill case study: A tutorial on processing CSV files
9 June 2016, TheServerSide.com

Using Apache Iceberg for Developing Modern Data Tables
3 October 2023, Open Source For You

Apache Drill Poised to Crack Tough Data Challenges
19 May 2015, Datanami

Apache Drill Eliminates ETL, Data Transformation for MapR Database
11 April 2016, The New Stack

provided by Google News

Share this page