DBMS > Axibase vs. Drizzle vs. mSQL vs. MySQL vs. Rockset

System Properties Comparison Axibase vs. Drizzle vs. mSQL vs. MySQL vs. Rockset

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

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used open source RDBMS

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Document store

Secondary database models

Document store
Spatial DBMS

Relational DBMS
Search engine

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

Score	0.21
Rank	#308	Overall
	#25	Time Series DBMS

Score	1.26
Rank	#163	Overall
	#74	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	1.07
Rank	#180	Overall
	#31	Document stores

Website

axibase.com/docs/atsd/finance

hughestech.com.au/products/msql

www.mysql.com

rockset.com

Technical documentation

dev.mysql.com/doc

docs.rockset.com

Developer

Axibase Corporation

Drizzle project, originally started by Brian Aker

Hughes Technologies

Oracle

since 2010, originally MySQL AB, then Sun

Rockset

Initial release

2013

2008

1994

1995

2019

Current release

15585

7.2.4, September 2012

4.4, October 2021

9.0.0, July 2024

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

GNU GPL

commercial

free licenses can be provided

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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

Java

C++

C and C++

C++

Server operating systems

Linux

FreeBSD
Linux
OS X

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

with proprietary extensions

Read-only SQL queries, including JOINs

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

JDBC

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

Supported programming languages

Go
Java
PHP
Python
R
Ruby

C
C++
Java
PHP

C
C++
Delphi
Java
Perl
PHP
Tcl

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

Go
Java
JavaScript (Node.js)
Python

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

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

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

Access rights for users and organizations can be defined via Rockset console

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.