DBMS > Dgraph vs. EsgynDB vs. Ignite vs. Infobright vs. RDF4J

System Properties Comparison Dgraph vs. EsgynDB vs. Ignite vs. Infobright vs. RDF4J

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Graph DBMS

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

RDF store

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

Score	1.48
Rank	#158	Overall
	#15	Graph DBMS

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	3.64
Rank	#89	Overall
	#13	Key-value stores
	#48	Relational DBMS

Score	1.00
Rank	#193	Overall
	#90	Relational DBMS

Score	0.71
Rank	#231	Overall
	#9	RDF stores

Website

dgraph.io

www.esgyn.cn

ignite.apache.org

ignitetech.com/softwarelibrary/infobrightdb

rdf4j.org

Technical documentation

dgraph.io/docs

apacheignite.readme.io/docs

rdf4j.org/documentation

Developer

Dgraph Labs, Inc.

Esgyn

Apache Software Foundation

Ignite Technologies Inc.; formerly InfoBright Inc.

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2016

2015

2005

2004

Current release

Apache Ignite 2.6

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Eclipse Distribution License (EDL), v1.0.

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++, Java

C++, Java, .Net

Java

Server operating systems

Linux
OS X
Windows

Linux

Linux
OS X
Solaris
Windows

Linux
Windows

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

RDF Schemas

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.

yes

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

yes (compute grid and cache interceptors can be used instead)

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication between multi datacenters

yes (replicated cache)

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

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

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Dgraph on AWS: Setting up a horizontally scalable graph database | Amazon Web Services
1 September 2020, AWS Blog

Dgraph Raises $6M in Seed Funding
20 July 2022, FinSMEs

Dgraph Rises to the Top Graph Database on GitHub With 11 G2 Badges and 11M Downloads
26 May 2021, Business Wire

Dgraph GraphQL database users detail graph use cases
20 April 2021, TechTarget

provided by Google News

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain Showcases Power of Apache Ignite at Community Over Code Conference
5 October 2023, Datanami

Apache Ignite: An Overview
6 September 2023, Open Source For You

ArcGIS and Apache Log4j Vulnerabilities
22 May 2023, Esri

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

provided by Google News

Share this page