DBMS > IRONdb vs. Oracle Berkeley DB vs. Spark SQL vs. SQLite

System Properties Comparison IRONdb vs. Oracle Berkeley DB vs. Spark SQL 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

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

Widely used in-process key-value store

Spark SQL is a component on top of 'Spark Core' for structured data processing

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	19.15
Rank	#33	Overall
	#20	Relational DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

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

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

spark.apache.org/sql

www.sqlite.org

Technical documentation

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

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

spark.apache.org/docs/latest/sql-programming-guide.html

www.sqlite.org/docs.html

Developer

Circonus LLC.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2017

1994

2014

2000

Current release

V0.10.20, January 2018

18.1.40, May 2020

3.5.0 ( 2.13), September 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

Apache 2.0

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

C and C++

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

Scala

Server operating systems

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X
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

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

yes

SQL interfaced based on SQLite is available

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

HTTP API

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.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

Java
Python
R
Scala

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

Automatic, metric affinity per node

none

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

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.