DBMS > Apache Impala vs. GridDB vs. SAP HANA vs. Titan

System Properties Comparison Apache Impala vs. GridDB vs. SAP HANA 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

Analytic DBMS for Hadoop

Scalable in-memory time series database optimized for IoT and Big Data

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

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Secondary database models

Document store

Key-value store
Relational DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

impala.apache.org

griddb.net

www.sap.com/products/hana.html

github.com/thinkaurelius/titan

Technical documentation

impala.apache.org/impala-docs.html

docs.griddb.net

help.sap.com/hana

github.com/thinkaurelius/titan/wiki

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Toshiba Corporation

SAP

Aurelius, owned by DataStax

Initial release

2013

2010

2012

Current release

4.1.0, June 2022

5.1, August 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

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

Appliance or cloud-service

Linux
OS X
Unix
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL-like DML and DDL statements

SQL92, SQL-like TQL (Toshiba Query Language)

yes

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

JDBC
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Clojure
Java
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate consistency within container, eventual consistency across containers

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 at container level

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

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Access rights for users can be defined per database

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.