DBMS > SAP HANA vs. Titan vs. YottaDB

System Properties Comparison SAP HANA vs. Titan vs. YottaDB

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

In-memory, column based data store. Available as appliance or cloud service

Titan is a Graph DBMS optimized for distributed clusters.

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Graph DBMS

Key-value store

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.20
Rank	#317	Overall
	#47	Key-value stores

Website

www.sap.com/products/hana.html

github.com/thinkaurelius/titan

yottadb.com

Technical documentation

help.sap.com/hana

github.com/thinkaurelius/titan/wiki

yottadb.com/resources/documentation

Developer

SAP

Aurelius, owned by DataStax

YottaDB, LLC

Initial release

2010

2012

2001

Current release

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache license, version 2.0

Open Source

AGPL 3.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

Appliance or cloud-service

Linux
OS X
Unix
Windows

Docker
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

by using the Octo plugin

APIs and other access methods

JDBC
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

Clojure
Java
Python

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

Transaction concepts

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

ACID

optimistic locking

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.

yes

User concepts

Access control

yes

User authentification and security via Rexster Graph Server

Users and groups based on OS-security mechanisms

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.