DBMS > AlaSQL vs. Drizzle vs. Ehcache vs. ObjectBox vs. RocksDB

System Properties Comparison AlaSQL vs. Drizzle vs. Ehcache vs. ObjectBox vs. RocksDB

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.

A widely adopted Java cache with tiered storage options

Extremely fast embedded database for small devices, IoT and Mobile

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store
Relational DBMS

Secondary database models

Time Series 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	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	1.20
Rank	#170	Overall
	#5	Object oriented DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

Technical documentation

github.com/AlaSQL/alasql

www.ehcache.org/documentation

docs.objectbox.io

github.com/facebook/rocksdb/wiki

Developer

Andrey Gershun & Mathias R. Wulff

Drizzle project, originally started by Brian Aker

Terracotta Inc, owned by Software AG

ObjectBox Limited

Facebook, Inc.

Initial release

2014

2008

2009

2017

2013

Current release

7.2.4, September 2012

3.10.0, March 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache License 2.0

Open Source

BSD

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

C++

Server operating systems

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

FreeBSD
Linux
OS X

All OS with a Java VM

Android
iOS
Linux
macOS
Windows

Linux

Data scheme

schema-free

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

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

yes

with proprietary extensions

APIs and other access methods

JavaScript API

JDBC

JCache

Proprietary native API

C++ API
Java API

Supported programming languages

JavaScript

C
C++
Java
PHP

Java

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

by using Terracotta Server

online/offline synchronization between client and server

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Tunable Consistency (Strong, Eventual, Weak)

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

ACID

yes

supports JTA and can work as an XA resource

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

using a tiered cache-storage approach

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

yes

More information provided by the system vendor

News

The first On-Device Vector Database: ObjectBox 4.0
16 May 2024

Edge AI: The era of on-device AI
23 April 2024

In-Memory Database Use Cases
15 February 2024

Data Viewer for Objects – announcing ObjectBox Admin
14 November 2023

Vector Databases for Edge AI
9 August 2023

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.