DBMS > BigObject vs. Datomic vs. SpaceTime vs. SQLite vs. TimesTen

System Properties Comparison BigObject vs. Datomic vs. SpaceTime vs. SQLite vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

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

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Widely used embeddable, in-process RDBMS

An in-memory SQL relational database that delivers microsecond response and high throughput for OLTP applications. TimesTen can be deployed as a standalone database or as a cache to a backend Oracle database.

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.13
Rank	#329	Overall
	#147	Relational DBMS

Score	1.55
Rank	#144	Overall
	#67	Relational DBMS

Score	0.00
Rank	#385	Overall
	#7	Spatial DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	1.26
Rank	#164	Overall
	#75	Relational DBMS

Website

bigobject.io

www.datomic.com

www.mireo.com/spacetime

www.sqlite.org

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

docs.bigobject.io

docs.datomic.com

www.sqlite.org/docs.html

docs.oracle.com/en/database/other-databases/timesten/index.html

Developer

BigObject, Inc.

Cognitect

Mireo

Dwayne Richard Hipp

Oracle

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2015

2012

2020

2000

1998

Current release

1.0.7180, July 2024

3.46.1 (13 August 2024), August 2024

Release 22.1

License

Commercial or Open Source

commercial

free community edition available

commercial

limited edition free

commercial

Open Source

Public Domain

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

Java, Clojure

C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

All OS with a Java VM

Linux

server-less

IBM AIX Power PC 64-bit
Linux arm64
Linux x86-64
Solaris SPARC 64
Solaris SPARC/x86
Solaris x86-64

Data scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

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

SQL-like DML and DDL statements

A subset of ANSI SQL is implemented

yes

SQL-92 is not fully supported

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ODBC
ODP.NET
Oracle Call Interface (OCI)
Pro*C/C++ programming interfaces
SQL and PL/SQL via JDBC

Supported programming languages

Clojure
Java

C#
C++
Python

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++
Java
Node.js
PL/SQL
Python

Server-side scripts

Stored procedures

Lua

yes

Transaction Functions

PL/SQL

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

Fixed-grid hypercubes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Real-time block device replication (DRBD)

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

by means of logfiles and checkpoints

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

yes

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.