DBMS > Dgraph vs. LevelDB vs. SAP Advantage Database Server vs. SQLite vs. XTDB

System Properties Comparison Dgraph vs. LevelDB vs. SAP Advantage Database Server vs. SQLite vs. XTDB

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Distributed and scalable native Graph DBMS

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

Low-cost RDBMS with access to ISAM and FoxPro data structures

Widely used embeddable, in-process RDBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

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

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

dgraph.io

github.com/google/leveldb

www.sap.com/products/advantage-database-server.html

www.sqlite.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

dgraph.io/docs

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

www.sqlite.org/docs.html

www.xtdb.com/docs

Developer

Dgraph Labs, Inc.

Google

Sybase, SAP

Dwayne Richard Hipp

Juxt Ltd.

Initial release

2016

2011

1993

2000

2019

Current release

1.23, February 2021

3.46.0 (23 May 2024), May 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD

commercial

Open Source

Public Domain

Open Source

MIT License

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++

Clojure

Server operating systems

Linux
OS X
Windows

Illumos
Linux
OS X
Windows

Linux
Windows

server-less

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes, extensible-data-notation format

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

SQL-92 is not fully supported

limited SQL, making use of Apache Calcite

APIs and other access methods

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

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP REST
JDBC

Supported programming languages

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

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Delphi
Perl
PHP

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

Clojure
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

none

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

none

yes, each node contains all data

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

via file-system locks

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

caching of (temporary) tables can be configured

yes

User concepts

Access control

Planned for future releases

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.