DBMS > Datomic vs. Google BigQuery vs. Riak TS vs. TerminusDB

System Properties Comparison Datomic vs. Google BigQuery vs. Riak TS vs. TerminusDB

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

Large scale data warehouse service with append-only tables

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

Primary database model

Relational DBMS

Time Series DBMS

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

www.datomic.com

cloud.google.com/bigquery

terminusdb.com

Technical documentation

docs.datomic.com

cloud.google.com/bigquery/docs

www.tiot.jp/riak-docs/riak/ts/latest

terminusdb.github.io/terminusdb/#

Developer

Cognitect

Google

Open Source, formerly Basho Technologies

DataChemist Ltd.

Initial release

2012

2010

2015

2018

Current release

1.0.7075, December 2023

3.0.0, September 2022

11.0.0, January 2023

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

GPL V3

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Clojure

Erlang

Prolog, Rust

Server operating systems

All OS with a Java VM

hosted

Linux
OS X

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

restricted

SQL

Support of SQL

yes

yes, limited

SQL-like query language (WOQL)

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Clojure
Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

JavaScript
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

in JavaScript

Erlang

yes

Triggers

By using transaction functions

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

none

Sharding

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

selectable replication factor

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

yes

in-memory journaling

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

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.