DBMS > Datomic vs. Graphite vs. Microsoft Azure Cosmos DB vs. PostGIS

System Properties Comparison Datomic vs. Graphite vs. Microsoft Azure Cosmos DB vs. PostGIS

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Globally distributed, horizontally scalable, multi-model database service

Spatial extension of PostgreSQL

Primary database model

Relational DBMS

Time Series 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	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

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

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Website

www.datomic.com

github.com/graphite-project/graphite-web

azure.microsoft.com/services/cosmos-db

postgis.net

Technical documentation

docs.datomic.com

graphite.readthedocs.io

learn.microsoft.com/azure/cosmos-db

postgis.net/documentation

Developer

Cognitect

Chris Davis

Microsoft

Initial release

2012

2006

2014

2005

Current release

1.0.7075, December 2023

3.4.2, February 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache 2.0

commercial

Open Source

GPL v2.0

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

Python

Server operating systems

All OS with a Java VM

Linux
Unix

hosted

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

HTTP API
Sockets

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

Supported programming languages

Clojure
Java

JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

yes

Transaction Functions

JavaScript

user defined functions

Triggers

By using transaction functions

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

none

Sharding

Implicit feature of the cloud service

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

none

yes

Implicit feature of the cloud service

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

locking

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 rights can be defined down to the item level

yes

based on PostgreSQL

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.