DBMS > Apache Drill vs. Graph Engine vs. H2 vs. Machbase Neo vs. SAP HANA

System Properties Comparison Apache Drill vs. Graph Engine vs. H2 vs. Machbase Neo vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

TimeSeries DBMS for AIoT and BigData

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

Primary database model

Document store
Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

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	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

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

Score	8.22
Rank	#50	Overall
	#32	Relational DBMS

Score	0.22
Rank	#324	Overall
	#29	Time Series DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Website

www.sap.com/products/hana.html

Technical documentation

drill.apache.org/docs

www.graphengine.io/docs/manual

www.h2database.com/html/main.html

machbase.com/dbms

help.sap.com/hana

Developer

Apache Software Foundation

Microsoft

Thomas Mueller

Machbase

SAP

Initial release

2012

2010

2005

2013

2010

Current release

1.20.3, January 2023

2.2.220, July 2023

V8.0, August 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

MIT License

Open Source

dual-licence (Mozilla public license, Eclipse public license)

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

.NET and C

Java

Server operating systems

Linux
OS X
Windows

.NET

All OS with a Java VM

Linux
macOS
Windows

Appliance or cloud-service

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

JDBC
ODBC

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

JDBC
ODBC

Supported programming languages

C++

C#
C++
F#
Visual Basic

Java

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Server-side scripts

Stored procedures

user defined functions

yes

Java Stored Procedures and User-Defined Functions

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

With clustering: 2 database servers on different computers operate on identical copies of a database

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

Depending on the underlying data source

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 capabilities

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

Depending on the underlying data source

yes

volatile and lookup table

yes

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

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.