DBMS > Datomic vs. OrigoDB vs. SQLite vs. TimescaleDB

System Properties Comparison Datomic vs. OrigoDB vs. SQLite vs. TimescaleDB

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

A fully ACID in-memory object graph database

Widely used embeddable, in-process RDBMS

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#19	Object oriented DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

Technical documentation

docs.datomic.com

origodb.com/docs

www.sqlite.org/docs.html

docs.timescale.com

Developer

Cognitect

Robert Friberg et al

Dwayne Richard Hipp

Timescale

Initial release

2012

2009

under the name LiveDB

2000

2017

Current release

1.0.7075, December 2023

3.46.0 (23 May 2024), May 2024

2.15.0, May 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

Public Domain

Open Source

Apache 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

Server operating systems

All OS with a Java VM

Linux
Windows

server-less

Linux
OS X
Windows

Data scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

not rigid because of 'dynamic typing' concept.

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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.

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP API

.NET Client API
HTTP API
LINQ

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Clojure
Java

.Net

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

By using transaction functions

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

horizontal partitioning

client side managed; servers are not synchronized

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Source-replica replication

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

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

yes

Write ahead log

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

Role based authorization

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.