DBMS > IRONdb vs. SQLite vs. Transbase vs. XTDB

System Properties Comparison IRONdb vs. SQLite vs. Transbase vs. XTDB

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 embeddable, in-process RDBMS

A resource-optimized, high-performance, universally applicable RDBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Time Series DBMS

Relational DBMS

Document store

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

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

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

www.sqlite.org

www.transaction.de/en/products/transbase.html

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

www.sqlite.org/docs.html

www.transaction.de/en/products/transbase/features.html

www.xtdb.com/docs

Developer

Circonus LLC.

Dwayne Richard Hipp

Transaction Software GmbH

Juxt Ltd.

Initial release

2017

2000

1987

2019

Current release

V0.10.20, January 2018

3.45.3 (15 April 2024), April 2024

Transbase 8.3, 2022

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Public Domain

commercial

free development license

Open Source

MIT License

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

Clojure

Server operating systems

Linux

server-less

FreeBSD
Linux
macOS
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

dynamic column types

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

not rigid because of 'dynamic typing' concept.

yes

yes, extensible-data-notation format

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.

Secondary indexes

yes

SQL

Support of SQL

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

yes

SQL-92 is not fully supported

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
JDBC

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

yes, in Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

none

Source-replica replication

yes, each node contains all data

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

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.