DBMS > AlaSQL vs. Hypertable vs. Oracle Berkeley DB vs. RocksDB vs. Rockset

System Properties Comparison AlaSQL vs. Hypertable vs. Oracle Berkeley DB vs. RocksDB vs. Rockset

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

JavaScript DBMS library

An open source BigTable implementation based on distributed file systems such as Hadoop

Widely used in-process key-value store

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

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Document store
Relational DBMS

Wide column store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Document store

Secondary database models

Relational DBMS
Search engine

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	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

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

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

alasql.org

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

rocksdb.org

rockset.com

Technical documentation

github.com/AlaSQL/alasql

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

github.com/facebook/rocksdb/wiki

docs.rockset.com

Developer

Andrey Gershun & Mathias R. Wulff

Hypertable Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Rockset

Initial release

2014

2009

1994

2013

2019

Current release

0.9.8.11, March 2016

18.1.40, May 2020

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

GNU version 3. Commercial license available

Open Source

commercial license available

Open Source

BSD

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

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

C++

Server operating systems

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

Linux
OS X
Windows

an inofficial Windows port is available

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

hosted

Data scheme

schema-free

Typing

predefined data types such as float or date

dynamic typing

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

ingestion from XML files supported

Secondary indexes

restricted

only exact value or prefix value scans

yes

all fields are automatically indexed

SQL

Support of SQL

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

yes

SQL interfaced based on SQLite is available

Read-only SQL queries, including JOINs

APIs and other access methods

JavaScript API

C++ API
Thrift

C++ API
Java API

HTTP REST

Supported programming languages

JavaScript

C++
Java
Perl
PHP
Python
Ruby

.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
C++
Go
Java
Perl
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor on file system level

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual 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

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

Access rights for users and organizations can be defined via Rockset console

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.