DBMS > AlaSQL vs. BaseX vs. Ehcache vs. PlanetScale vs. RocksDB

System Properties Comparison AlaSQL vs. BaseX vs. Ehcache vs. PlanetScale vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

A widely adopted Java cache with tiered storage options

Scalable, distributed, serverless MySQL database platform built on top of Vitess

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

Primary database model

Document store
Relational DBMS

Secondary database models

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	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

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

Website

Technical documentation

github.com/AlaSQL/alasql

docs.basex.org

www.ehcache.org/documentation

planetscale.com/docs

github.com/facebook/rocksdb/wiki

Developer

Andrey Gershun & Mathias R. Wulff

BaseX GmbH

Terracotta Inc, owned by Software AG

PlanetScale

Facebook, Inc.

Initial release

2014

2007

2009

2020

2013

Current release

10.7, August 2023

3.10.0, March 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

BSD license

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

BSD

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

JavaScript

Java

C++

Server operating systems

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

Linux
OS X
Windows

All OS with a Java VM

Docker
Linux
macOS

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

XQuery supports types

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

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

JCache

ADO.NET
JDBC
MySQL protocol
ODBC

C++ API
Java API

Supported programming languages

JavaScript

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

Java

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

via events

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

by using Terracotta Server

Multi-source replication
Source-replica replication

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)

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

multiple readers, single writer

yes

supports JTA and can work as an XA resource

ACID at shard level

yes

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

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

Users with fine-grained authorization concept on 4 levels

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.