DBMS > Datomic vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. OrigoDB

System Properties Comparison Datomic vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. OrigoDB

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

Globally distributed, horizontally scalable, multi-model database service

Fully managed big data interactive analytics platform

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

column oriented

Document store
Object oriented DBMS

Secondary database models

Spatial DBMS

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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

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	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#19	Object oriented DBMS

Website

www.datomic.com

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/services/data-explorer

origodb.com

Technical documentation

docs.datomic.com

learn.microsoft.com/azure/cosmos-db

docs.microsoft.com/en-us/azure/data-explorer

origodb.com/docs

Developer

Cognitect

Microsoft

Robert Friberg et al

Initial release

2012

2014

2019

2009

under the name LiveDB

Current release

1.0.7075, December 2023

cloud service with continuous releases

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

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

Server operating systems

All OS with a Java VM

hosted

Linux
Windows

Data scheme

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

User defined using .NET types and collections

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.

yes

can be achieved using .NET

Secondary indexes

yes

All properties auto-indexed by default

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

Kusto Query Language (KQL), SQL subset

APIs and other access methods

RESTful HTTP API

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

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

.NET Client API
HTTP API
LINQ

Supported programming languages

Clojure
Java

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

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

.Net

Server-side scripts

Stored procedures

yes

Transaction Functions

JavaScript

Yes, possible languages: KQL, Python, R

yes

Triggers

By using transaction functions

JavaScript

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

horizontal partitioning

client side managed; servers are not synchronized

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

yes

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

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

Write ahead log

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

Access rights can be defined down to the item level

Azure Active Directory Authentication

Role based authorization

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.