DBMS > AlaSQL vs. IRONdb vs. Oracle Berkeley DB vs. SQLite

System Properties Comparison AlaSQL vs. IRONdb vs. Oracle Berkeley DB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

JavaScript DBMS library

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Widely used in-process key-value store

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Time Series DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

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

Score	0.42
Rank	#264	Overall
	#42	Document stores
	#122	Relational DBMS

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

alasql.org

www.circonus.com/solutions/time-series-database/

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

www.sqlite.org

Technical documentation

github.com/AlaSQL/alasql

docs.circonus.com/irondb/category/getting-started

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

www.sqlite.org/docs.html

Developer

Andrey Gershun & Mathias R. Wulff

Circonus LLC.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Dwayne Richard Hipp

Initial release

2014

2017

1994

2000

Current release

V0.10.20, January 2018

18.1.40, May 2020

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

commercial license available

Open Source

Public Domain

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

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

Server operating systems

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

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL

Support of SQL

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

SQL interfaced based on SQLite is available

yes

SQL-92 is not fully supported

APIs and other access methods

JavaScript API

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

JavaScript

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

.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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes, in Lua

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

configurable replication factor, datacenter aware

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate consistency per node, eventual consistency across nodes

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

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

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.