DBMS > Hazelcast vs. Postgres-XL vs. PouchDB vs. SAP HANA vs. Titan

System Properties Comparison Hazelcast vs. Postgres-XL vs. PouchDB vs. SAP HANA 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

A widely adopted in-memory data grid

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

JavaScript DBMS with an API inspired by CouchDB

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

JSON support with IMDG 3.12

Document store
Spatial 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	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

hazelcast.com

www.postgres-xl.org

pouchdb.com

www.sap.com/products/hana.html

github.com/thinkaurelius/titan

Technical documentation

hazelcast.org/imdg/docs

www.postgres-xl.org/documentation

pouchdb.com/guides

help.sap.com/hana

github.com/thinkaurelius/titan/wiki

Developer

Hazelcast

Apache Software Foundation

SAP

Aurelius, owned by DataStax

Initial release

2008

2014

since 2012, originally named StormDB

2012

2010

2012

Current release

5.3.6, November 2023

10 R1, October 2018

7.1.1, June 2019

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Mozilla public license

Open Source

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

Java

JavaScript

Java

Server operating systems

All OS with a Java VM

Linux
macOS

server-less, requires a JavaScript environment (browser, Node.js)

Appliance or cloud-service

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

schema-free

yes

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.

yes

the object must implement a serialization strategy

yes

XML type, but no XML query functionality

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL-like query language

yes

distributed, parallel query execution

yes

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP REST

only for PouchDB Server
JavaScript API

JDBC
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

JavaScript

Clojure
Java
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

user defined functions

View functions in JavaScript

SQLScript, R

yes

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

with a proxy-based framework, named couchdb-lounge

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

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 or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Eventual Consistency

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

one or two-phase-commit; repeatable reads; read commited

ACID

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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 access control

fine grained access rights according to SQL-standard

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.