DBMS > AlaSQL vs. Ehcache vs. Firebase Realtime Database vs. Kinetica vs. RocksDB

System Properties Comparison AlaSQL vs. Ehcache vs. Firebase Realtime Database vs. Kinetica vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

A widely adopted Java cache with tiered storage options

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Fully vectorized database across both GPUs and CPUs

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

Primary database model

Document store
Relational DBMS

Secondary database models

Spatial DBMS
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	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

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

Website

alasql.org

www.ehcache.org

firebase.google.com/products/realtime-database

www.kinetica.com

rocksdb.org

Technical documentation

github.com/AlaSQL/alasql

www.ehcache.org/documentation

firebase.google.com/docs/database

docs.kinetica.com

github.com/facebook/rocksdb/wiki

Developer

Andrey Gershun & Mathias R. Wulff

Terracotta Inc, owned by Software AG

Google

acquired by Google 2014

Kinetica

Facebook, Inc.

Initial release

2014

2009

2012

2013

Current release

3.10.0, March 2022

7.1, August 2021

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT-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, C++

C++

Server operating systems

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

All OS with a Java VM

hosted

Linux

Data scheme

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.

SQL-like DML and DDL statements

APIs and other access methods

JavaScript API

JCache

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

C++ API
Java API

Supported programming languages

JavaScript

Java

Java
JavaScript
Objective-C

C++
Java
JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

Triggers

yes

Cache Event Listeners

Callbacks are triggered when data changes

yes

triggers when inserted values for one or more columns fall within a specified range

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

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

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency or Eventual Consistency depending on configuration

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

yes

supports JTA and can work as an XA resource

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

GPU vRAM or System RAM

yes

User concepts

Access control

yes, based on authentication and database rules

Access rights for users and roles on table level

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.