DBMS > Apache Impala vs. Dgraph vs. SAP HANA vs. Valentina Server

System Properties Comparison Apache Impala vs. Dgraph vs. SAP HANA vs. Valentina Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Distributed and scalable native Graph DBMS

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

Object-relational database and reports server

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

Secondary database models

Document store

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

impala.apache.org

dgraph.io

www.sap.com/products/hana.html

www.valentina-db.net

Technical documentation

impala.apache.org/impala-docs.html

dgraph.io/docs

help.sap.com/hana

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Dgraph Labs, Inc.

SAP

Paradigma Software

Initial release

2013

2016

2010

1999

Current release

4.1.0, June 2022

2.0 SPS07 (April 4, 2023), April 2023

5.7.5

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

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

C++

Server operating systems

Linux

Linux
OS X
Windows

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JDBC
ODBC

ODBC

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

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

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Synchronous replication via Raft

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

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

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Planned for future releases

yes

fine grained access rights according to SQL-standard

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.