DBMS > Datomic vs. RRDtool vs. SQLite vs. Warp 10

System Properties Comparison Datomic vs. RRDtool vs. SQLite vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Widely used embeddable, in-process RDBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

www.datomic.com

oss.oetiker.ch/rrdtool

www.sqlite.org

www.warp10.io

Technical documentation

docs.datomic.com

oss.oetiker.ch/rrdtool/doc

www.sqlite.org/docs.html

www.warp10.io/content/02_Getting_started

Developer

Cognitect

Tobias Oetiker

Dwayne Richard Hipp

SenX

Initial release

2012

1999

2000

2015

Current release

1.0.6735, June 2023

1.8.0, 2022

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

GPL V2 and FLOSS

Open Source

Public Domain

Open Source

Apache License 2.0

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

Java, Clojure

Implementations in Java (e.g. RRD4J) and C# available

Java

Server operating systems

All OS with a Java VM

HP-UX
Linux

server-less

Linux
OS X
Windows

Data scheme

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

in-process shared library
Pipes

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API
Jupyter
WebSocket

Supported programming languages

Clojure
Java

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
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

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

WarpScript

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

based on HBase

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

by using the rrdcached daemon

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.