DBMS > Amazon DynamoDB vs. GraphDB vs. Tarantool vs. Titan

System Properties Comparison Amazon DynamoDB vs. GraphDB vs. Tarantool vs. Titan

Please select another system to include it in the comparison.

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

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

Enterprise-ready RDF and graph database with efficient reasoning, cluster and external index synchronization support. It supports also SQL JDBC access to Knowledge Graph and GraphQL over SPARQL.

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Document store
Key-value store

Graph DBMS
RDF store

Document store
Key-value store
Relational DBMS

Graph DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	3.25
Rank	#91	Overall
	#7	Graph DBMS
	#4	RDF stores

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

aws.amazon.com/dynamodb

www.ontotext.com

www.tarantool.io

github.com/thinkaurelius/titan

Technical documentation

docs.aws.amazon.com/dynamodb

graphdb.ontotext.com/documentation

www.tarantool.io/en/doc

github.com/thinkaurelius/titan/wiki

Social network pages

Developer

Amazon

Ontotext

Aurelius, owned by DataStax

Initial release

2012

2000

2008

2012

Current release

10.4, October 2023

2.10.0, May 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Some plugins of GraphDB Workbench are open sourced

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

Java

C and C++

Java

Server operating systems

hosted

All OS with a Java VM
Linux
OS X
Windows

BSD
Linux
macOS

Linux
OS X
Unix
Windows

Data scheme

schema-free

schema-free and OWL/RDFS-schema support; RDF shapes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

yes, supports real-time synchronization and indexing in SOLR/Elastic search/Lucene and GeoSPARQL geometry data indexes

yes

SQL

Support of SQL

stored SPARQL accessed as SQL using Apache Calcite through JDBC/ODBC

Full-featured ANSI SQL support

APIs and other access methods

RESTful HTTP API

GeoSPARQL
GraphQL
GraphQL Federation
Java API
JDBC
RDF4J API
RDFS
RIO
Sail API
Sesame REST HTTP Protocol
SPARQL 1.1

Open binary protocol

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Clojure
Java
Python

Server-side scripts

Stored procedures

well-defined plugin interfaces; JavaScript server-side extensibility

Lua, C and SQL stored procedures

yes

Triggers

yes

by integration with AWS Lambda

yes, before/after data modification events, on replication events, client session events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency, Eventual consistency (configurable in cluster mode per master or individual client request)

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Constraint checking

yes

Relationships in graph

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

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

In-memory capabilities

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

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

Default Basic authentication through RDF4J client, or via Java when run with cURL, default token-based in the Workbench or via Rest API, optional access through OpenID or Kerberos single sign-on.

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

User authentification and security via Rexster Graph Server

More information provided by the system vendor

Specific characteristics

Ontotext GraphDB is a semantic database engine that allows organizations to build...
» more

Competitive advantages

GraphDB allows you to link text and data in big knowledge graphs. It’s easy to experiment...
» more

Typical application scenarios

Metadata enrichment and management, linked data publishing, semantic inferencing...
» more

Key customers

GraphDB provides a platform for building next-generation AI and Knowledge Graph...
» more

Market metrics

GraphDB is the most utilized semantic triplestore for mission-critical enterprise...
» more

Licensing and pricing models

GraphDB Free is a non-commercial version and is free to use. GraphDB Enterprise edition...
» more

News

Riding the Databricks Wave with Hybrid Knowledge Graphs
6 June 2024

Matching Skills and Candidates with Graph RAG
31 May 2024

A Triple Store RAG Retriever
29 May 2024

Integrating GraphDB with Relational Database Systems
23 May 2024

Understanding the Graph Center of Excellence
17 May 2024

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.