DBMS > Datomic vs. EsgynDB vs. Microsoft Azure Cosmos DB vs. SQream DB

System Properties Comparison Datomic vs. EsgynDB vs. Microsoft Azure Cosmos DB vs. SQream DB

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Globally distributed, horizontally scalable, multi-model database service

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.47
Rank	#145	Overall
	#66	Relational DBMS

Score	0.15
Rank	#325	Overall
	#145	Relational DBMS

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

Score	0.63
Rank	#229	Overall
	#107	Relational DBMS

Website

www.datomic.com

www.esgyn.cn

azure.microsoft.com/services/cosmos-db

sqream.com

Technical documentation

docs.datomic.com

learn.microsoft.com/azure/cosmos-db

docs.sqream.com

Developer

Cognitect

Esgyn

Microsoft

SQream Technologies

Initial release

2012

2015

2014

2017

Current release

1.0.7180, July 2024

2022.1.6, December 2022

License

Commercial or Open Source

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

C++, CUDA, Haskell, Java, Scala

Server operating systems

All OS with a Java VM

Linux

hosted

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes, ANSI Standard SQL Types

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

yes

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

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

.Net
JDBC
ODBC

Supported programming languages

Clojure
Java

All languages supporting JDBC/ODBC/ADO.Net

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

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

Java Stored Procedures

JavaScript

user defined functions in Python

Triggers

By using transaction functions

JavaScript

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

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication between multi datacenters

yes

Implicit feature of the cloud service

none

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

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

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

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.