DBMS > Amazon Neptune vs. Microsoft Azure Cosmos DB vs. Rockset vs. Sphinx vs. Titan

System Properties Comparison Amazon Neptune vs. Microsoft Azure Cosmos DB vs. Rockset vs. Sphinx vs. Titan

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.

Description

Fast, reliable graph database built for the cloud

Globally distributed, horizontally scalable, multi-model database service

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Open source search engine for searching in data from different sources, e.g. relational databases

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Graph DBMS
RDF store

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Search engine

Graph DBMS

Secondary database models

Spatial DBMS

Relational DBMS
Search engine

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

Score	2.20
Rank	#119	Overall
	#9	Graph DBMS
	#5	RDF stores

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

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

aws.amazon.com/neptune

azure.microsoft.com/services/cosmos-db

rockset.com

sphinxsearch.com

github.com/thinkaurelius/titan

Technical documentation

aws.amazon.com/neptune/developer-resources

learn.microsoft.com/azure/cosmos-db

docs.rockset.com

sphinxsearch.com/docs

github.com/thinkaurelius/titan/wiki

Developer

Amazon

Microsoft

Rockset

Sphinx Technologies Inc.

Aurelius, owned by DataStax

Initial release

2017

2014

2019

2001

2012

Current release

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence available

Open Source

Apache license, version 2.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

C++

Java

Server operating systems

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

yes

All properties auto-indexed by default

all fields are automatically indexed

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

Read-only SQL queries, including JOINs

SQL-like query language (SphinxQL)

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

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

HTTP REST

Proprietary protocol

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

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

Go
Java
JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Clojure
Java
Python

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Automatic sharding

Sharding

Partitioning is done manually, search queries against distributed index is supported

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

yes

Implicit feature of the cloud service

yes

none

yes

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

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Relationships in graph

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

with encyption-at-rest

yes

The original contents of fields are not stored in the Sphinx index.

yes

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

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Access rights can be defined down to the item level

Access rights for users and organizations can be defined via Rockset console

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.