DBMS > Drizzle vs. Lovefield vs. MySQL vs. Sqrrl vs. Warp 10

System Properties Comparison Drizzle vs. Lovefield vs. MySQL vs. Sqrrl vs. Warp 10

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.

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

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

Embeddable relational database for web apps written in pure JavaScript

Widely used open source RDBMS

Adaptable, secure NoSQL built on Apache Accumulo

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.22
Rank	#306	Overall
	#138	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.06
Rank	#351	Overall
	#35	Time Series DBMS

Website

google.github.io/lovefield

www.mysql.com

sqrrl.com

www.warp10.io

Technical documentation

github.com/google/lovefield/blob/master/docs/spec_index.md

dev.mysql.com/doc

www.warp10.io/content/02_Getting_started

Developer

Drizzle project, originally started by Brian Aker

Google

Oracle

since 2010, originally MySQL AB, then Sun

Amazon

originally Sqrrl Data, Inc.

SenX

Initial release

2008

2014

1995

2012

2015

Current release

7.2.4, September 2012

2.1.12, February 2017

9.0.0, July 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

Apache License 2.0

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

C++

JavaScript

C and C++

Java

Server operating systems

FreeBSD
Linux
OS X

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

tested with Chrome, Firefox, IE, Safari

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

via JavaScript builder pattern

yes

with proprietary extensions

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

HTTP API
Jupyter
WebSocket

Supported programming languages

C
C++
Java
PHP

JavaScript

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

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

WarpScript

Triggers

hooks for callbacks inside the server can be used.

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

making use of Hadoop

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Multi-source replication
Source-replica replication

selectable replication factor

making use of Hadoop

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Immediate Consistency

based on HBase

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

Atomic updates per row, document, or graph entity

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

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users with fine-grained authorization concept

no user groups or roles

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.