DBMS > Dgraph vs. InfinityDB vs. LevelDB vs. MySQL vs. YottaDB

System Properties Comparison Dgraph vs. InfinityDB vs. LevelDB vs. MySQL vs. YottaDB

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

A Java embedded Key-Value Store which extends the Java Map interface

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

Widely used open source RDBMS

A fast and solid embedded Key-value store

Primary database model

Graph DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Key-value store

Secondary database models

Document store
Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.00
Rank	#378	Overall
	#57	Key-value stores

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.20
Rank	#317	Overall
	#47	Key-value stores

Website

dgraph.io

boilerbay.com

github.com/google/leveldb

www.mysql.com

yottadb.com

Technical documentation

dgraph.io/docs

boilerbay.com/infinitydb/manual

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

dev.mysql.com/doc

yottadb.com/resources/documentation

Developer

Dgraph Labs, Inc.

Boiler Bay Inc.

Google

Oracle

since 2010, originally MySQL AB, then Sun

YottaDB, LLC

Initial release

2016

2002

2011

1995

2001

Current release

4.0

1.23, February 2021

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

BSD

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL 3.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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C++

C and C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Illumos
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux

Data scheme

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

yes

with proprietary extensions

by using the Octo plugin

APIs and other access methods

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

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

ADO.NET
JDBC
ODBC
Proprietary native API

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

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

Java

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID

not for MyISAM storage engine

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

Users and groups based on OS-security mechanisms

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.