DBMS > Dgraph vs. H2 vs. MarkLogic vs. SQLite

System Properties Comparison Dgraph vs. H2 vs. MarkLogic vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

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

Operational and transactional Enterprise NoSQL database

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.48
Rank	#158	Overall
	#15	Graph DBMS

Score	8.22
Rank	#50	Overall
	#32	Relational DBMS

Score	6.50
Rank	#56	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#5	Search engines

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

dgraph.io/docs

www.h2database.com/html/main.html

docs.marklogic.com

www.sqlite.org/docs.html

Developer

Dgraph Labs, Inc.

Thomas Mueller

MarkLogic Corp.

Dwayne Richard Hipp

Initial release

2016

2005

2001

2000

Current release

2.2.220, July 2023

11.0, December 2022

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

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

commercial

restricted free version is available

Open Source

Public Domain

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

Java

C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Linux
OS X
Windows

server-less

Data scheme

schema-free

yes

schema-free

Schema can be enforced

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

yes

SQL92

yes

SQL-92 is not fully supported

APIs and other access methods

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

JDBC
ODBC

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

Java

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

yes

via XQuery or JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

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

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

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

can act as a resource manager in an XA/JTA transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

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

yes, with Range Indexes

yes

User concepts

Access control

Planned for future releases

fine grained access rights according to SQL-standard

Role-based access control at the document and subdocument levels

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.