DBMS > AlaSQL vs. Amazon Redshift vs. Firebase Realtime Database vs. Oracle Berkeley DB vs. Transwarp Hippo

System Properties Comparison AlaSQL vs. Amazon Redshift vs. Firebase Realtime Database vs. Oracle Berkeley DB vs. Transwarp Hippo

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Large scale data warehouse service for use with business intelligence tools

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

Widely used in-process key-value store

Cloud-native distributed Vector DBMS that supports storage, retrieval, and management of massive vector-based datasets

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Vector DBMS

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

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	0.05
Rank	#386	Overall
	#14	Vector DBMS

Website

alasql.org

aws.amazon.com/redshift

firebase.google.com/products/realtime-database

www.oracle.com/database/technologies/related/berkeleydb.html

www.transwarp.cn/en/subproduct/hippo

Technical documentation

github.com/AlaSQL/alasql

docs.aws.amazon.com/redshift

firebase.google.com/docs/database

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Andrey Gershun & Mathias R. Wulff

Amazon (based on PostgreSQL)

Google

acquired by Google 2014

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2014

2012

1994

2023

Current release

18.1.40, May 2020

1.0, May 2023

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

commercial license 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

JavaScript

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

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

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
macOS

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Vector, Numeric and String

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

only with the Berkeley DB XML edition

Secondary indexes

restricted

yes

SQL

Support of SQL

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

yes

does not fully support an SQL-standard

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JavaScript API

JDBC
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

RESTful HTTP API

Supported programming languages

JavaScript

All languages supporting JDBC/ODBC

Java
JavaScript
Objective-C

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C++
Java
Python

Server-side scripts

Stored procedures

user defined functions

in Python

limited functionality with using 'rules'

Triggers

yes

Callbacks are triggered when data changes

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

Role based access control and fine grained access rights

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.