DBMS > Dgraph vs. InfinityDB vs. SQLite vs. Yaacomo vs. Yanza

System Properties Comparison Dgraph vs. InfinityDB vs. SQLite vs. Yaacomo vs. Yanza

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Distributed and scalable native Graph DBMS

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

Widely used embeddable, in-process RDBMS

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Time Series DBMS for IoT Applications

Primary database model

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	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

dgraph.io

boilerbay.com

www.sqlite.org

yaacomo.com

yanza.com

Technical documentation

dgraph.io/docs

boilerbay.com/infinitydb/manual

www.sqlite.org/docs.html

Developer

Dgraph Labs, Inc.

Boiler Bay Inc.

Dwayne Richard Hipp

Q2WEB GmbH

Yanza

Initial release

2016

2002

2000

2009

2015

Current release

4.0

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Public Domain

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

server-less

Android
Linux
Windows

Windows

Data scheme

schema-free

yes

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

yes

dynamic column types

yes

schema-free

Typing

predefined data types such as float or date

yes

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

yes

not rigid because of 'dynamic typing' concept.

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

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

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

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

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC

HTTP API

Supported programming languages

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

Java

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

yes

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

none

Source-replica replication

none

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

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

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.