DBMS > atoti vs. Datomic vs. Google BigQuery vs. RethinkDB

System Properties Comparison atoti vs. Datomic vs. Google BigQuery vs. RethinkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

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

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Primary database model

Object oriented DBMS

Relational DBMS

Document store

Secondary database models

Spatial DBMS

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

Score	0.56
Rank	#245	Overall
	#10	Object oriented DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.74
Rank	#105	Overall
	#19	Document stores

Website

atoti.io

www.datomic.com

cloud.google.com/bigquery

rethinkdb.com

Technical documentation

docs.atoti.io

docs.datomic.com

cloud.google.com/bigquery/docs

rethinkdb.com/docs

Developer

ActiveViam

Cognitect

Google

The Linux Foundation

since July 2017

Initial release

2012

2010

2009

Current release

1.0.6735, June 2023

2.4.1, August 2020

License

Commercial or Open Source

commercial

free versions available

commercial

limited edition free

commercial

Open Source

Apache Version 2

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

Java, Clojure

C++

Server operating systems

All OS with a Java VM

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

Multidimensional Expressions (MDX)

yes

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

Supported programming languages

Clojure
Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Server-side scripts

Stored procedures

Python

yes

Transaction Functions

user defined functions

in JavaScript

Triggers

By using transaction functions

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

none

But extensive use of caching in the application peers

none

Sharding

range based

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

MVCC based

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

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

yes

users and table-level permissions

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.