DBMS > Datomic vs. Google BigQuery vs. IRONdb vs. JaguarDB vs. Microsoft Azure Table Storage

System Properties Comparison Datomic vs. Google BigQuery vs. IRONdb vs. JaguarDB vs. Microsoft Azure Table Storage

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Performant, highly scalable DBMS for AI and IoT applications

A Wide Column Store for rapid development using massive semi-structured datasets

Primary database model

Relational DBMS

Time Series DBMS

Key-value store
Vector DBMS

Wide column 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.06
Rank	#381	Overall
	#59	Key-value stores
	#14	Vector DBMS

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Website

www.datomic.com

cloud.google.com/bigquery

www.circonus.com/solutions/time-series-database/

www.jaguardb.com

azure.microsoft.com/en-us/services/storage/tables

Technical documentation

docs.datomic.com

cloud.google.com/bigquery/docs

docs.circonus.com/irondb/category/getting-started

www.jaguardb.com/support.html

Developer

Cognitect

Google

Circonus LLC.

DataJaguar, Inc.

Microsoft

Initial release

2012

2010

2017

2015

2012

Current release

1.0.7075, December 2023

V0.10.20, January 2018

3.3 July 2023

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

GPL V3.0

commercial

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

C and C++

C++

the server part. Clients available in other languages

Server operating systems

All OS with a Java VM

hosted

Linux

hosted

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

yes

SQL-like query language (Circonus Analytics Query Language: CAQL)

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

HTTP API

JDBC
ODBC

RESTful HTTP API

Supported programming languages

Clojure
Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

in JavaScript

yes, in Lua

Triggers

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

none

Automatic, metric affinity per node

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

configurable replication factor, datacenter aware

Multi-source replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Eventual Consistency

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

optimistic locking

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 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)

rights management via user accounts

Access rights based on private key authentication or shared access signatures

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.