DBMS > Microsoft Azure Cosmos DB vs. RavenDB vs. Spark SQL vs. Titan vs. Yanza

System Properties Comparison Microsoft Azure Cosmos DB vs. RavenDB vs. Spark SQL vs. Titan vs. Yanza

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

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

Description

Globally distributed, horizontally scalable, multi-model database service

Open Source Operational and Transactional Enterprise NoSQL Document Database

Spark SQL is a component on top of 'Spark Core' for structured data processing

Titan is a Graph DBMS optimized for distributed clusters.

Time Series DBMS for IoT Applications

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

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

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

azure.microsoft.com/services/cosmos-db

ravendb.net

spark.apache.org/sql

github.com/thinkaurelius/titan

yanza.com

Technical documentation

learn.microsoft.com/azure/cosmos-db

ravendb.net/docs

spark.apache.org/docs/latest/sql-programming-guide.html

github.com/thinkaurelius/titan/wiki

Developer

Microsoft

Hibernating Rhinos

Apache Software Foundation

Aurelius, owned by DataStax

Yanza

Initial release

2014

2010

2014

2012

2015

Current release

5.4, July 2022

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

Open Source

Apache 2.0

Open Source

Apache license, version 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Scala

Java

Server operating systems

hosted

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Windows

Linux
OS X
Unix
Windows

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language (RQL)

SQL-like DML and DDL statements

APIs and other access methods

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

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

JDBC
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

HTTP API

Supported programming languages

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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java
Python
R
Scala

Clojure
Java
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

yes, utilizing Spark Core

yes

via pluggable storage backends

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Multi-source replication

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

via Faunus, a graph analytics engine

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

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Access rights can be defined down to the item level

Authorization levels configured per client per database

User authentification and security via Rexster Graph Server

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.