DBMS > Apache Drill vs. Datomic vs. Microsoft Azure Cosmos DB vs. SpaceTime

System Properties Comparison Apache Drill vs. Datomic vs. Microsoft Azure Cosmos DB vs. SpaceTime

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Spatial DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Website

drill.apache.org

www.datomic.com

azure.microsoft.com/services/cosmos-db

www.mireo.com/spacetime

Technical documentation

drill.apache.org/docs

docs.datomic.com

learn.microsoft.com/azure/cosmos-db

Developer

Apache Software Foundation

Cognitect

Microsoft

Mireo

Initial release

2012

2014

2020

Current release

1.20.3, January 2023

1.0.6735, June 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

limited edition free

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

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

hosted

Linux

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

A subset of ANSI SQL is implemented

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

RESTful HTTP API

Supported programming languages

C++

Clojure
Java

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C#
C++
Python

Server-side scripts

Stored procedures

user defined functions

yes

Transaction Functions

JavaScript

Triggers

By using transaction functions

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

Implicit feature of the cloud service

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

yes

Implicit feature of the cloud service

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

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.

Depending on the underlying data source

yes

recommended only for testing and development

User concepts

Access control

Depending on the underlying data source

Access rights can be defined down to the item level

yes

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.