DBMS > Datomic vs. Graphite vs. MongoDB

System Properties Comparison Datomic vs. Graphite vs. MongoDB

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

One of the most popular document stores available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Relational DBMS

Time Series DBMS

Document store

Secondary database models

Spatial DBMS
Search engine

integrated Lucene index, currently in MongoDB Atlas only.
Time Series DBMS

Time Series Collections introduced in Release 5.0

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

Score	2.25
Rank	#133	Overall
	#65	Relational DBMS

Score	6.59
Rank	#63	Overall
	#4	Time Series DBMS

Score	458.78
Rank	#5	Overall
	#1	Document stores

Website

www.datomic.com

github.com/graphite-project/graphite-web

www.mongodb.com

Technical documentation

docs.datomic.com

graphite.readthedocs.io

docs.mongodb.com/manual

Developer

Cognitect

Chris Davis

MongoDB, Inc

Initial release

2012

2006

2009

Current release

1.0.6362, January 2022

6.0.1, August 2022

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache 2.0

Open Source

MongoDB Inc.'s Server Side Public License v1. Prior versions were published under GNU AGPL v3.0. Commercial licenses are also available.

Cloud-based only

Only available as a cloud service

MongoDB available as DBaaS (MongoDB Atlas)

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

ScaleGrid for MongoDB Database: Fully managed hosting for MongoDB Database on a wide variety of cloud providers and On-Premises. Automate your management, scaling and backups through one centralized platform.

Implementation language

Java, Clojure

Python

C++

Server operating systems

All OS with a Java VM

Linux
Unix

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

Although schema-free, documents of the same collection often follow the same structure. Optionally impose all or part of a schema by defining a JSON schema.

Typing

predefined data types such as float or date

yes

Numeric data only

yes

string, integer, double, decimal, boolean, date, object_id, geospatial

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

Read-only SQL queries via the MongoDB Connector for BI

APIs and other access methods

RESTful HTTP API

HTTP API
Sockets

proprietary protocol using JSON

Supported programming languages

Clojure
Java

JavaScript (Node.js)
Python

Actionscript

unofficial driver
C
C#
C++
Clojure

unofficial driver
ColdFusion

unofficial driver
D

unofficial driver
Dart

unofficial driver
Delphi

unofficial driver
Erlang
Go
Groovy

unofficial driver
Haskell
Java
JavaScript
Lisp

unofficial driver
Lua

unofficial driver
MatLab

unofficial driver
Perl
PHP
PowerShell

unofficial driver
Prolog

unofficial driver
Python
R

unofficial driver
Ruby
Rust
Scala
Smalltalk

unofficial driver
Swift

Server-side scripts

Stored procedures

yes

Transaction Functions

JavaScript

Triggers

By using transaction functions

yes

in MongoDB Atlas only

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

none

Sharding

Partitioned by hashed, ranged, or zoned sharding keys. Live resharding allows users to change their shard keys as an online operation with zero downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

none

Multi-Source deployments with MongoDB Atlas Global Clusters
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

Transaction concepts

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

ACID

Multi-document ACID Transactions with snapshot isolation

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

optional, enabled by default

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

In-memory storage engine introduced with MongoDB version 3.2

User concepts

Access control

Access rights for users and roles

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.