DBMS > Badger vs. Dgraph vs. EJDB vs. SAP HANA

System Properties Comparison Badger vs. Dgraph vs. EJDB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

Distributed and scalable native Graph DBMS

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

github.com/dgraph-io/badger

dgraph.io

github.com/Softmotions/ejdb

www.sap.com/products/hana.html

Technical documentation

godoc.org/github.com/dgraph-io/badger

dgraph.io/docs

github.com/Softmotions/ejdb/blob/master/README.md

help.sap.com/hana

Developer

DGraph Labs

Dgraph Labs, Inc.

Softmotions

SAP

Initial release

2017

2016

2012

2010

Current release

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

GPLv2

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

server-less

Appliance or cloud-service

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

APIs and other access methods

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

in-process shared library

JDBC
ODBC

Supported programming languages

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

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Server-side scripts

Stored procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication via Raft

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

Planned for future releases

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.