DBMS > Dgraph vs. Interbase vs. LevelDB vs. SAP HANA

System Properties Comparison Dgraph vs. Interbase vs. LevelDB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Light-weight proven RDBMS

originally from Borland

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

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

Primary database model

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	1.39
Rank	#155	Overall
	#15	Graph DBMS

Score	3.78
Rank	#77	Overall
	#41	Relational DBMS

Score	2.33
Rank	#111	Overall
	#19	Key-value stores

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

dgraph.io

www.embarcadero.com/products/interbase

github.com/google/leveldb

www.sap.com/products/hana.html

Technical documentation

dgraph.io/docs

docs.embarcadero.com/products/interbase

github.com/google/leveldb/blob/main/doc/index.md

help.sap.com/hana

Developer

Dgraph Labs, Inc.

Embarcadero

Google

SAP

Initial release

2016

1984

2011

2010

Current release

InterBase 2020, December 2019

1.23, February 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

BSD

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
OS X
Windows

Android
iOS
Linux
OS X
Windows

Illumos
Linux
OS X
Windows

Appliance or cloud-service

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.

export as XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC

JDBC
ODBC

Supported programming languages

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

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Interbase Change Views

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

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

Planned for future releases

fine grained access rights according to SQL-standard

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.