DBMS > OrigoDB vs. SAP HANA vs. Sphinx vs. Titan

System Properties Comparison OrigoDB vs. SAP HANA vs. Sphinx 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

A fully ACID in-memory object graph database

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

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

Document store
Object oriented DBMS

Relational DBMS

Search engine

Graph DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

origodb.com

www.sap.com/products/hana.html

sphinxsearch.com

github.com/thinkaurelius/titan

Technical documentation

origodb.com/docs

help.sap.com/hana

sphinxsearch.com/docs

github.com/thinkaurelius/titan/wiki

Developer

Robert Friberg et al

SAP

Sphinx Technologies Inc.

Aurelius, owned by DataStax

Initial release

2009

under the name LiveDB

2010

2001

2012

Current release

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

License

Commercial or Open Source

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

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

C++

Java

Server operating systems

Linux
Windows

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

Data scheme

yes

Typing

predefined data types such as float or date

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

APIs and other access methods

.NET Client API
HTTP API
LINQ

JDBC
ODBC

Proprietary protocol

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

.Net

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Clojure
Java
Python

Server-side scripts

Stored procedures

yes

SQLScript, R

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

yes

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

Source-replica replication

yes

none

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

depending on model

yes

Relationships in graph

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

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

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

User concepts

Access control

Role based authorization

yes

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.