DBMS > AlaSQL vs. Drizzle vs. Heroic vs. SWC-DB vs. Vitess

System Properties Comparison AlaSQL vs. Drizzle vs. Heroic vs. SWC-DB vs. Vitess

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

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A high performance, scalable Wide Column DBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store
Relational DBMS

Secondary database models

Time Series DBMS

Document store
Spatial 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	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

alasql.org

github.com/spotify/heroic

github.com/kashirin-alex/swc-db
www.swcdb.org

vitess.io

Technical documentation

github.com/AlaSQL/alasql

spotify.github.io/heroic

vitess.io/docs

Developer

Andrey Gershun & Mathias R. Wulff

Drizzle project, originally started by Brian Aker

Spotify

Alex Kashirin

The Linux Foundation, PlanetScale

Initial release

2014

2008

2014

2020

2013

Current release

7.2.4, September 2012

0.5, April 2021

15.0.2, December 2022

License

Commercial or Open Source

Open Source

MIT-License

Open Source

GNU GPL

Open Source

Apache 2.0

Open Source

GPL V3

Open Source

Apache Version 2.0, commercial licenses available

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

Java

C++

Server operating systems

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

FreeBSD
Linux
OS X

Linux

Docker
Linux
macOS

Data scheme

schema-free

yes

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

via Elasticsearch

yes

SQL

Support of SQL

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

yes

with proprietary extensions

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JavaScript API

JDBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Proprietary protocol
Thrift

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

JavaScript

C
C++
Java
PHP

C++

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users with fine-grained authorization concept

no user groups or roles

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

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

provided by Google News

2022 All O-Zone Football Team
17 December 2022, Ozarks Sports Zone

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

provided by Google News

Share this page