DBMS > Dolt vs. Microsoft Azure Cosmos DB vs. OrientDB vs. ToroDB

System Properties Comparison Dolt vs. Microsoft Azure Cosmos DB vs. OrientDB vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

Globally distributed, horizontally scalable, multi-model database service

Multi-model DBMS (Document, Graph, Key/Value)

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Graph DBMS
Key-value store

Document store

Secondary database models

Document store

Spatial DBMS

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

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

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Website

github.com/dolthub/dolt
www.dolthub.com

azure.microsoft.com/services/cosmos-db

orientdb.org

github.com/torodb/server

Technical documentation

docs.dolthub.com

learn.microsoft.com/azure/cosmos-db

www.orientdb.com/docs/last/index.html

Developer

DoltHub Inc

Microsoft

OrientDB LTD; CallidusCloud; SAP

8Kdata

Initial release

2018

2014

2010

2016

Current release

3.2.29, March 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache version 2

Open Source

AGPL-V3

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

Server operating systems

Linux
macOS
Windows

hosted

All OS with a Java JDK (>= JDK 6)

All OS with a Java 7 VM

Data scheme

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

string, integer, double, boolean, date, object_id

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

yes

SQL

Support of SQL

yes

SQL-like query language

SQL-like query language, no joins

APIs and other access methods

CLI Client
HTTP REST

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

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

currently in alpha release

JavaScript

Java, Javascript

Triggers

yes

JavaScript

Hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

yes

Implicit feature of the cloud service

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

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

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

Access rights can be defined down to the item level

Access rights for users and roles; record level security configurable

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.