DBMS > AgensGraph vs. Apache Phoenix vs. Machbase Neo vs. SAP HANA

System Properties Comparison AgensGraph vs. Apache Phoenix vs. Machbase Neo vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

A scale-out RDBMS with evolutionary schema built on Apache HBase

TimeSeries DBMS for AIoT and BigData

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

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Time Series DBMS

Relational 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.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

bitnine.net/agensgraph

phoenix.apache.org

machbase.com

www.sap.com/products/hana.html

Technical documentation

bitnine.net/documentation

phoenix.apache.org

machbase.com/dbms

help.sap.com/hana

Developer

Bitnine Global Inc.

Apache Software Foundation

Machbase

SAP

Initial release

2016

2014

2013

2010

Current release

2.1, December 2018

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

V8.0, August 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

commercial

free test version available

commercial

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

Linux
OS X
Windows

Linux
Unix
Windows

Linux
macOS
Windows

Appliance or cloud-service

Data scheme

depending on used data model

yes

late-bound, schema-on-read capabilities

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

Cypher Query Language
JDBC

JDBC

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

JDBC
ODBC

Supported programming languages

C
Java
JavaScript
Python

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Server-side scripts

Stored procedures

yes

user defined functions

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

In-memory capabilities

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

yes

volatile and lookup table

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

simple password-based access control

yes

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.