DBMS > AgensGraph vs. IRONdb vs. SQLite vs. TerminusDB

System Properties Comparison AgensGraph vs. IRONdb vs. SQLite vs. TerminusDB

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

Multi-model database supporting relational and graph data models and built upon PostgreSQL

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

Widely used embeddable, in-process RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Graph DBMS
Relational DBMS

Time Series DBMS

Relational DBMS

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	0.17
Rank	#320	Overall
	#29	Graph DBMS
	#143	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Website

bitnine.net/agensgraph

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

www.sqlite.org

terminusdb.com

Technical documentation

bitnine.net/documentation

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

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

Developer

Bitnine Global Inc.

Circonus LLC.

Dwayne Richard Hipp

DataChemist Ltd.

Initial release

2016

2017

2000

2018

Current release

2.1, December 2018

V0.10.20, January 2018

3.46.1 (13 August 2024), August 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Public Domain

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

Linux
OS X
Windows

Linux

server-less

Linux

Data scheme

depending on used data model

schema-free

yes

dynamic column types

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

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

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

Cypher Query Language
JDBC

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C
Java
JavaScript
Python

.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

JavaScript
Python

Server-side scripts

Stored procedures

yes

yes, in Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Automatic, metric affinity per node

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

configurable replication factor, datacenter aware

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

Role-based 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.