DBMS > Graph Engine vs. Netezza vs. Postgres-XL vs. SAP HANA vs. TerminusDB

System Properties Comparison Graph Engine vs. Netezza vs. Postgres-XL vs. SAP HANA vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Data warehouse and analytics appliance part of IBM PureSystems

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

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
RDF store

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

www.graphengine.io

www.ibm.com/products/netezza

www.postgres-xl.org

www.sap.com/products/hana.html

terminusdb.com

Technical documentation

www.graphengine.io/docs/manual

www.postgres-xl.org/documentation

help.sap.com/hana

terminusdb.github.io/terminusdb/#

Developer

Microsoft

IBM

SAP

DataChemist Ltd.

Initial release

2010

2000

2014

since 2012, originally named StormDB

2010

2018

Current release

10 R1, October 2018

2.0 SPS07 (April 4, 2023), April 2023

11.0.0, January 2023

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Mozilla public license

commercial

Open Source

GPL V3

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

.NET and C

Prolog, Rust

Server operating systems

.NET

Linux

included in appliance

Linux
macOS

Appliance or cloud-service

Linux

Data scheme

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

yes

SQL-like query language (WOQL)

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
OLE DB

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

JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C#
C++
F#
Visual Basic

C
C++
Fortran
Java
Lua
Perl
Python
R

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

JavaScript
Python

Server-side scripts

Stored procedures

yes

user defined functions

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

horizontal partitioning

yes

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

in-memory journaling

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept

fine grained access rights according to SQL-standard

yes

Role-based access control

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.