DBMS > IRONdb vs. RavenDB vs. SQLite vs. SwayDB vs. Teradata Aster

System Properties Comparison IRONdb vs. RavenDB vs. SQLite vs. SwayDB vs. Teradata Aster

Editorial information provided by DB-Engines

Name

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

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Widely used embeddable, in-process RDBMS

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Platform for big data analytics on multistructured data sources and types

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

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

ravendb.net

www.sqlite.org

swaydb.simer.au

Technical documentation

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

ravendb.net/docs

www.sqlite.org/docs.html

Developer

Circonus LLC.

Hibernating Rhinos

Dwayne Richard Hipp

Simer Plaha

Teradata

Initial release

2017

2010

2000

2018

2005

Current release

V0.10.20, January 2018

5.4, July 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

Open Source

Public Domain

Open Source

GNU Affero GPL V3.0

commercial

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

Scala

Server operating systems

Linux

Linux
macOS
Raspberry Pi
Windows

server-less

Linux

Data scheme

schema-free

yes

dynamic column types

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

not rigid because of 'dynamic typing' concept.

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.

yes

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

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

SQL-like query language (RQL)

yes

SQL-92 is not fully supported

yes

APIs and other access methods

HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC
OLE DB

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
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Java
Kotlin
Scala

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes, in Lua

yes

R packages

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Multi-source replication

none

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

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

ACID, Cluster-wide transaction available

ACID

Atomic execution of operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

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

Authorization levels configured per client per database

fine grained access rights according to SQL-standard

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.